When a rchitecture becomes pluggable, developers can handoff work to trusted third party dependencies. Developers can start to think of the differ ent parts of the application as their own units with their own concerns. When each part of the application runs in its own container, different parts of the application will not have compatibility issues as they would running on the same machine. The “it runs fine on my machine” risks are minimized when moving from develop ment to production environments. Creating images for different parts of the application allows the infrastructure to be standardized making it easier to manage. The base of this stack utiliz es D ocker to containerize the application. Utilizing some awesome microservices we have managed to create a tech stack that allows developers to spend less time configuring and more time developing.
T eams at UDig have been looking for ways to minimize this initial project infrastructure workload. A development team can spend a lot of time working on these features, which take s away time that could be spent working on the core application funct ionality. Th is list could include user management, HTTPS, deployment strategy and project organization.
There is a laundry list of needs a web application has that are important for getting an application to production. However, once a project moves out of the proof of concept phase, there is a lot of development that needs to be done which only indirectly helps make an idea a reality. Whether creat ing a new site, the next big social media platform or j ust trying to make a process workflow easier, th e idea is the driving force where teams want to spend most of their time perfecting the user experience. Every new application starts with an idea.