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: definition
Unfortunately, there is no universally acknowledged definition for the
term *microservice*. In the context of this course the following definition will be used:

> **Microservices** are independently deployable modules.

For example, an **e-commerce system** can be divided into modules for:
- ordering
- registration
- product search

Normally, all of these modules would be implemented together in one application. In
this case, **a change in one of the modules** can only be brought into production by bringing a **new version of the entire application** with
all its modules into production. However, when the modules are implemented as microservices, the ordering process cannot only be **changed independently of the other modules**, but it can even be brought into production independently.

This speeds up deployment and reduces the number of necessary tests since only a single module needs to be deployed.  Due to this greater
level of decoupling, a large project can turn into a number of
smaller projects. Each project is in charge of an individual microservice.

To achieve this at the technical level, **every microservice has to be an independent process**. A better solution for decoupling
microservices is to provide an independent virtual machine or Docker container for each microservice. 

In that case, a deployment will replace the Docker container of an individual microservice with a new Docker container, which starts the new version and its direct requests. The other microservices will not be affected if such an approach is used.

In this lesson, we'll look at an overview of what to expect from this chapter!

Preface

Microservices

Micro and Macro Architecture

Migration

Docker

Technical Micro Architecture

Appendix

Introduction

Microservices: definition #