Tradeoffs, Prioritizing Advantages, & Levels
Explore the tradeoffs involved in adopting microservices and learn how to prioritize advantages like scaling development and continuous delivery. Understand the two levels of microservices division—domain and technical—and how these impact deployment and scalability. This lesson helps you evaluate scenarios to increase business value effectively through microservice architecture.
Prioritizing advantages #
Which of the discussed reasons for switching to microservices is the most important depends on the individual scenario. The use of microservices in a greenfield system is the one exception.
More often, a deployment monolith is replaced by a microservice system (see chapter 4). In that case, different advantages are relevant.
-
The easier scaling of development can be an important reason for the introduction of microservices in such a scenario. Often, it is impossible to work quickly enough with a large number of developers on a single deployment monolith.
-
The easy migration away from the legacy deployment monolith facilitates the introduction of microservices in such a scenario.
-
Continuous delivery is often an additional goal. The aim is to increase the speed and reliability with which changes can be brought into production.
The scaling of development is ...