In the world of software architecture, there are many “-ilities” you must take into consideration with every project. Prioritizing them is necessary because the client will optimistically ask that you do all of them. To help you out, here is a quick list outlining my top 7 default “-ilities” in the order that I prioritize them:
By now, it’s apparent to cybersecurity teams everywhere that the proverbial container genie is out of the bottle. Developers have widely embraced containers because they make building and deploying so-called cloud native applications simpler than ever. Not only do containers eliminate much of the friction typically associated with moving application code from testing through to production, but application code packaged up as containers can also run anywhere. All the dependencies associated with any application are included within the containerized application. That makes a containerized application highly portable across virtual machines or bare metal servers running in a local data center or on a public cloud.
In this article, we will look at several problems that every developer who uses a boilerplate can face:
How to customize your project
How to store it in your repository and still be able to pull all updates
All app templates and boilerplates are built to implement all possible functions and features. But, of course, it’s real life, and somebody would like to change your nice fonts, colors, pictures, icons, add more pages, change the structure, database models, change styles, et cetera, not to mention the code base itself.
In our boilerplate, we were trying to find a golden mean - to make everything as much customizable as possible but leave some things not changeable at all - to avoid unnecessary clutter. So, it’s only about technologies: we use PostgreSQL for the database and ReactJS/Bootstrap for the front end.
