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

When migrating to microservices, it is **important to know the objectives for taking this step**. Depending on the
reasons that led to this decision, the procedure for implementing them may vary.



# Microservices offer a fresh start

Especially when replacing legacy systems, microservices have several advantages. Let's discuss them.

The code of the legacy system no longer needs to be used in the new microservices because the microservices are implemented separately from the legacy system. The **microservices offer an unencumbered restart**. 

The code of a legacy system is often no longer maintainable, and the technologies are frequently outdated. Therefore, reusing the old code would hinder the development of a clean new system. 

Microservices thus solve the most important challenges when dealing with legacy systems, because otherwise, a restart is difficult.

Migration to microservices has the potential to solve the problem with the legacy system. After migration to microservices, further migrations can be limited to one or a few microservices. A migration of the entire system will probably not be necessary again. 

A typical **reason for a system migration is outdated technology**. In a microservices system, such a migration can take place step by step -- that is, microservice by microservice. 

Another migration reason is an **unmaintainable system**. In this case, each microservice can be replaced individually.



In this lesson, we'll discuss a few common reasons for migrating to a microservices architecture.

Preface

Microservices

Micro and Macro Architecture

Migration

Docker

Technical Micro Architecture

Appendix

Reasons for Migrating