This course covers everything related to microservices, including principles and concepts of micro and macro architectures and technical microarchitectures.

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

## Robustness

Microservice systems are more robust. 

When a memory leak exists in a microservice, only this microservice is affected and crashes. The other microservices keep running. Of course, they have to compensate for the failure of the crashed microservice; this is called **resilience**.

To achieve resilience, microservices can cache values and use them in case of a problem.  Alternatively, there might be a fallback to a simplified algorithm.

Without resilience, the **availability of a microservice system might be
a problem**.  It is likely that a microservice will fail for any reason.
- For example, due to the distribution into several processes, many more servers are involved in the system. Each of these servers can potentially fail.
- Communication between microservices occurs via the network, which can also fail. Therefore, microservices need to implement resilience to achieve robustness.




# Robustness

Microservice systems are more robust. 

When a memory leak exists in a microservice, only this microservice is affected and crashes. The other microservices keep running. Of course, they have to compensate for the failure of the crashed microservice; this is called **resilience**.

To achieve resilience, microservices can cache values and use them in case of a problem.  Alternatively, there might be a fallback to a simplified algorithm.

Without resilience, the **availability of a microservice system might be
a problem**.  It is likely that a microservice will fail for any reason.
- For example, due to the distribution into several processes, many more servers are involved in the system. Each of these servers can potentially fail.
- Communication between microservices occurs via the network, which can also fail. Therefore, microservices need to implement resilience to achieve robustness.




In this lesson, we'll continue our discussion of the advantages of microservices.

Preface

Microservices

Micro and Macro Architecture

Migration

Docker

Technical Micro Architecture

Appendix

More on Advantages

Robustness #