Every developer deserves a deployment

As developers, we want to keep our work momentum while intermediately doing integration testing in a real cloud environment. But, if the environment is shared with other developers on our team, we run into a common set of problems: overriding each other’s work, coordinating who’s testing right now and waiting in line for others to finish.

A common practice to deal with these problems is to work with _branch deployments _where developers create an entirely separate deployment for their project branch. When done and integration is needed, they deploy to a shared deployment.

Cleanup as a Service

Of course, the problem with creating ad-hoc deployments all over the place is that eventually, someone will have to clean them up. Either because one might have an OCD, and it hurts their brain to see all that clutter (hello 👋 ), or that some resources from these deployments might cost money if not removed. Over time, the costs can accumulate, and the cleanup work will get more challenging and more error-prone if automated with scripts.

#devops #ttl #aws #altostra #development