12 Deploying your microservices
This chapter covers
- Understanding why the DevOps movement is critical to microservices
- Configuring the core Amazon infrastructure used by Ostock services
- Manually deploying Ostock services to Amazon
- Designing a build and deployment pipeline for your services
- Moving from continuous integration to continuous deployment
- Treating your infrastructure as code
- Building the immutable server
- Testing in deployment
- Deploying your application to the cloud
We’re almost at the end of the book, but not the end of our microservices journey. While most of this book has focused on designing, building, and operationalizing Spring-based microservices using the Spring Cloud technology, we haven’t yet touched on how to build and deploy microservices. Creating a build and deployment pipeline might seem like a mundane task, but in reality, it’s one of the most critical pieces of our microservices architecture.
Why? Remember, one of the key advantages of a microservices architecture is that microservices are small units of code that can be quickly built, modified, and deployed to production independently of one another. The small size of the service means that new features (and critical bug fixes) can be delivered with a high degree of velocity. Velocity is the keyword here because velocity implies that little to no friction exists between making a new feature or fixing a bug and getting our service deployed. Lead times for deployment should be minutes, not days.