Chapter 7. Build

We’ve spent a lot of time covering the design aspects of microservices, but we need to start getting a bit deeper into how your development process may need to change in order to accommodate this new style of architecture. In the following chapters we’ll look at how we deploy and test our microservices, but before that we need to look at what comes first - what happens when a developer has a change ready to check in?

We’ll start this exploration by reviewing some foundational concepts - Continuous Integration and Continuous Delivery. They’re important concepts no matter what kind of systems architecture you might be using, but microservices open up a host of unique questions. From there we’ll look at pipelines, and different ways of managing source code for your services.

A Brief Introduction to Continuous Integration

Continuous integration (CI) has been around for a number of years, however It’s worth spending a bit of time going over the basics, as especially when we think about the mapping between microservices, builds, and version control repositories - there are some different options to consider.

With CI, the core goal is to keep everyone in sync with each other on a frequent basis, which ...

Get Building Microservices, 2nd Edition now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.