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

## New microservices
Creating a new microservice is very easy with Spring Boot.
A **build script** and a **main class** are enough, as shown in the example [simplest-spring-boot](https://github.com/ewolff/spring-boot-demos/tree/master/simplest-spring-boot). 

To further simplify the creation of a new microservice, a **template** can be created. The template only needs to be adapted for a new microservice. 

>**Settings** for the configuration of the microservices or for logging can be defined in the template. 

Thus, a template simplifies the creation of new microservices and facilitates compliance with macro architecture rules.

A particularly easy way to create a new Spring Boot project is to use http://start.spring.io/. 

The developer must select the build tool, the programming language, and a Spring Boot version. 

In addition, they can select different starters. Based on this, the website then creates a project that can be the basis for the implementation of a microservice.

# New microservices
Creating a new microservice is very easy with Spring Boot.
A **build script** and a **main class** are enough, as shown in the example [simplest-spring-boot](https://github.com/ewolff/spring-boot-demos/tree/master/simplest-spring-boot). 

To further simplify the creation of a new microservice, a **template** can be created. The template only needs to be adapted for a new microservice. 

>**Settings** for the configuration of the microservices or for logging can be defined in the template. 

Thus, a template simplifies the creation of new microservices and facilitates compliance with macro architecture rules.

A particularly easy way to create a new Spring Boot project is to use http://start.spring.io/. 

The developer must select the build tool, the programming language, and a Spring Boot version. 

In addition, they can select different starters. Based on this, the website then creates a project that can be the basis for the implementation of a microservice.

In this lesson, we'll be talking about microservice resilience and the creation of new microservices with Spring.

Preface

Microservices

Micro and Macro Architecture

Migration

Docker

Technical Micro Architecture

Appendix

Spring Boot for Microservices: New Microservices & Resilience

New microservices #