Gain insights into microservice principles, their pros and cons, Micro and Macro architecture, migration strategies, Docker's role, and technologies to effectively implement microservices.

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


# Microservices for scaling development

One reason for the use of microservices is the **easy scalability of development**.  Large teams often have to work together on complex
projects. With the help of microservices, the projects can be divided
into smaller units that can work independently of each other.

* For example, the **teams** responsible for an individual microservice **can make most technology decisions on their own**. 

- When the microservices are delivered as Docker containers, **each Docker container only has to offer an interface** for the other containers.
-  The **internal structure of the containers does not matter** as long as the interface is present and functions correctly. Therefore, it is irrelevant which programming language a microservice is written in. Consequently, the responsible team can make such decisions on their own. Of course, the selection of programming languages can be restricted in order to avoid increased complexity. However, even if the choice of the programming language in a project has been restricted, a team can still independently use an updated library with a bug fix for their microservice.
  
- As stated in the [last lesson](https://www.educative.io/courses/introduction-microservice-principles-concepts/introduction-N7Y2ZzKNl1p), when a new feature only requires changes in one microservice, it **can not only be developed independently, but it can also be brought into production on its own**. This allows the teams to work on features completely independently.

Thus, with the help of microservices, **teams can act independently regarding domain logic and technology**. This **minimizes the
coordination effort** required for large projects.

There are a number of reasons  why we should use microservices. 
Let's discuss them in this lesson.

Preface

Microservices

Micro and Macro Architecture

Migration

Docker

Technical Micro Architecture

Appendix

Advantages

Microservices for scaling development #