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

# Reactive programming
One way to implement a microservice is reactive programming. Oftentimes it is stated that microservices must be implemented with reactive technologies. 

This section discusses what *reactive* actually is and determines whether reactive technologies are truly needed for microservices.

Similar to microservices, reactive has an ambiguous definition. 

The [Reactive Manifesto](http://www.reactivemanifesto.org/) defines the term “reactive” based on the following characteristics:

## Responsive
- **Responsive** means that the system **responds as fast as possible**.

 ### Resilient
- Because of **resilience** the system **remains available** even if parts fail.
## Elastic
- The system can deal with different levels of load, for instance by using additional
resources. After the load peak subsides the resources are freed again.

## Asynchronous communication
- The system uses asynchronous communication (message-driven).

These characteristics are useful for microservices. They pretty much correspond to the features discussed in chapter 2 as essential characteristics of microservices.

At first sight, it seems that microservices, in fact, must be written with **reactive technologies.**

In this lesson, we'll discuss the concept of reactive programming and its relation to microservices.

Preface

Microservices

Micro and Macro Architecture

Migration

Docker

Technical Micro Architecture

Appendix

Reactive Programming

Reactive programming #

Responsive #

Resilient #

Elastic #