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


# Increased operations effort

- The *operation* of a microservice system **requires more effort than running a deployment monolith**. 
    - This is due to the fact that in a microservice system, many more deployable units exist that all have to be deployed and monitored. 
   - This is feasible only when the operation is largely automated and the correct functioning of the microservices is guaranteed via appropriate monitoring.

# Must Be Independently Deployable

- Microservices have to be **independently deployable**. For example, dividing them, into Docker containers is a prerequisite for this, but it is not enough on its own. 
- Changes to interfaces must be implemented in such a way that an independent deployment of individual microservices is still possible. 
    - For example, the microservice which implements the interface has to offer the new and the old interface. Then this microservice can be deployed without requiring that the calling microservice be deployed at the same time.

# Testing must be independent
- Also, **testing must be independent**.  When all microservices have to be tested together, one microservice can block the test stage and prevent the deployment of the other microservices making testing much harder. 

- Due to the split into microservices, there are more interfaces to test, and **testing has to be independent for both sides of the interface**. 




In this lesson, we'll look at possible challenges involved in a microservice architecture.

Preface

Microservices

Micro and Macro Architecture

Migration

Docker

Technical Micro Architecture

Appendix

Challenges

Increased operations effort #

Must Be Independently Deployable #