docker_ms2_v3.tar.gz

SpringBoot

test

SpringMain

ms-1-scs-esi

SpringMain-copy

scs-esi

scs-esi-copy

scs-esi-up

Microservices are one of the most important and popular software architecture trends. This architecture forms the base for a lot of companies including: Amazon, Netflix, Spotify, and Uber. 

In this course you’ll learn microservices in depth and understand reasons for and against microservices. Beyond that, you’ll learn about Micro and Macro architecture, strategies for migrating old systems, the role of Docker in this architecture, and technologies for implementing microservices. 

After taking this course, you’ll be better equipped to implement microservices for your own use.

An Introduction to Microservice Principles and Concepts

## 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](https://www.educative.io/courses/introduction-microservice-principles-concepts/introduction-N0WmwlRxKxN)). 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 not the only scenario for a migration. For example, when a **single Scrum team** wants to implement a system with microservices, **scaling development would not be a sensible reason**
since the organization of development is not large enough for this.  However, **other reasons are possible**. Continuous delivery, technical reasons like robustness, independent scaling, free technology choice, or sustainable development all play a role in such a scenario.

In the end, it is important to **focus on increasing the business value**. Depending on the scenario, an advantage in one of the
previously mentioned areas might make the company more profitable or competitive, for example, faster time to market or better
reliability of the system.



# 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](https://www.educative.io/courses/introduction-microservice-principles-concepts/introduction-N0WmwlRxKxN)). 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 not the only scenario for a migration. For example, when a **single Scrum team** wants to implement a system with microservices, **scaling development would not be a sensible reason**
since the organization of development is not large enough for this.  However, **other reasons are possible**. Continuous delivery, technical reasons like robustness, independent scaling, free technology choice, or sustainable development all play a role in such a scenario.

In the end, it is important to **focus on increasing the business value**. Depending on the scenario, an advantage in one of the
previously mentioned areas might make the company more profitable or competitive, for example, faster time to market or better
reliability of the system.



In this lesson, we'll look at some ways we can prioritize advantages of the microservice architecture and some potential trade-offs that should be considered.

Preface

Microservices

Micro and Macro Architecture

Migration

Docker

Technical Micro Architecture

Appendix

Tradeoffs, Prioritizing Advantages, & Levels

Prioritizing advantages #