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


## Micro architectural decisions
If decisions can actually be **different for each microservice**, then they are part of the **micro architecture**. 

Decisions at the micro architecture level are better suited to the self-organization of teams and use the technical freedom offered by microservices. 

Even if decisions are part of the micro architecture,  a team can still standardize because using technologies with which other teams already had positive experiences decreases the risk and allows for synergy.

## Macro architectural decisions
The **macro architecture**, on the other hand,
contains those parts of the architecture that **apply uniformly to all microservices**. 

The division into these two levels gives the individual microservices freedom, while simultaneously ensuring the integrity of the overall system.

In all cases, decisions must be made explicitly. The teams must
consciously deal with the macro architecture and the freedoms in micro
architecture. Micro and macro architecture form a trade-off which is different in each project.


# Micro architectural decisions
If decisions can actually be **different for each microservice**, then they are part of the **micro architecture**. 

Decisions at the micro architecture level are better suited to the self-organization of teams and use the technical freedom offered by microservices. 

Even if decisions are part of the micro architecture,  a team can still standardize because using technologies with which other teams already had positive experiences decreases the risk and allows for synergy.

# Macro architectural decisions
The **macro architecture**, on the other hand,
contains those parts of the architecture that **apply uniformly to all microservices**. 

The division into these two levels gives the individual microservices freedom, while simultaneously ensuring the integrity of the overall system.

In all cases, decisions must be made explicitly. The teams must
consciously deal with the macro architecture and the freedoms in micro
architecture. Micro and macro architecture form a trade-off which is different in each project.

In this lesson, we'll formally conclude this chapter with some notes regarding decisions at the micro and macro architectural level.

Microservices

Micro and Macro Architecture

Migration

Docker

Technical Micro Architecture

Appendix

Conclusion

Chapter Conclusion

Micro architectural decisions #