Deep dive into fundamental knowledge about microservices and background information about the concepts behind the microservices architecture approach.

Microservices Architecture

In this module we’ll learn about microservices in depth and understand the reasons for using and not using microservices. We’ll also learn about micro and macro architecture, strategies for migrating old systems, the role of Docker in this architecture, and technologies for implementing microservices like Spring Boot and Go.

After this module, you’ll be better equipped to implement microservices.

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.

Microservices

Micro and Macro Architecture

Migration

Docker

Technical Micro Architecture

Appendix

Conclusion

Spring Boot for Microservices: New Microservices & Resilience

New microservices #