Building Microservices with Go

Deployment

Since we have all our application code build, tested and packaged, it is time to think about deploying it into production. We need to start thinking about our infrastructure as immutable; that is, we will not make changes to the infrastructure but replace it instead. The levels at which this occurs can be many. For example, we have our container scheduler, which only runs the containers. When we deploy an update to our application binary, we are replacing a container on the scheduler, not refreshing the application in it. Containers give us one level of immutability; the other is the scheduler itself. To operate successful continuous delivery, the setup of this facet also needs to be automated. We need to think of our infrastructure ...