Before we start building our microservices, we should be clear about a few of their basic aspects, such as what factors to consider when sizing our microservices and how to ensure that they are isolated from the rest of the system.
As the name suggests, microservices should be micro. But what is micro? Microservices are all about size and granularity. To understand this better, let's consider the application discussed in Chapter 1, An Introduction to Microservices.
We want the teams working on this project to stay synchronized at all times with respect to their code. Staying synchronized is even more important when we release the complete project. We first needed to decompose our application and its specific parts into smaller functionalities/segments of the main service. Let's discuss the factors that need to be considered for the...