![]() These costs are not only in infrastructure costs, but also in the time your team members spend fixing, maintaining, and updating the environments. The costs of maintaining one or more static environments that sit idle for a long time can add up. This time leads to different dependency versions and bugs that are due to environment quirks and not necessarily code changes. While it depends on how you initially created the environments, and if you used any form of “infrastructure-as-code” tooling, long-living static environments can fall out of synchronization with each other. In the case of microservices, that environment likely also needs ephemeral support services to properly test code changes, such as a pre-seeded database, or a messaging bus. If you are using a microservices architecture, then an environment could be just one application component. If your application has a monolith architecture, then an environment needs to mimic your entire application. ![]() Maintaining static environments for particular purposes such as testing is better than not maintaining them, but are counter-intuitive if you want to switch to a continuous development workflow.īefore moving any further, it’s worth clarifying what an environment could be. That they remain the same for a long time, and are long-lived or static is important. These are typically something like “development”, “testing”, “staging”, and “production”, but the names are not the important part. We are now in something of a transition phase, and many development teams still maintain different environments for their workflow. We lovingly tended remote development environments to help us ensure that our code worked on something vaguely resembling a production environment before we pushed changes live. ![]() We found and used tools such as virtual machines and vagrant to help mitigate these issues on local machines. Developer environments have existed for some time, many of us remember trying to emulate expensive web hosting environments on our personal machines, and as they often varied so much, hitting the infamous “works on my machine” problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |