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

## Summary
- Migration to microservices is the typical approach for the introduction of microservices.  Implementing a completely new system with microservices is the exception, but of course, it is also possible. 


- One of the most important advantages of microservices is that they **work well for scenarios other than greenfield projects**.

- Choosing the **right migration strategy** is a complex task. It **depends on the legacy system and migration goals**. This chapter shows a starting point from which each project must develop its own strategy.

- Because of the benefits of migration, microservices should be considered in any project meant to modernize a legacy system. Microservices enable step-by-step modernization, in which completely different technologies can be used. This is very helpful.

- The **migration strategy can have a significant impact** on the architecture and technology selection. A split into microservices similar to the split of the modules in the legacy system can greatly simplify migration. Such a compromise has far-reaching consequences and can lead to a worse target architecture,
but it can still make sense.

- Finally, it must be possible to actually implement the architecture, and for this, a simple approach for the migration into the architecture is essential.

# Summary
- Migration to microservices is the typical approach for the introduction of microservices.  Implementing a completely new system with microservices is the exception, but of course, it is also possible. 


- One of the most important advantages of microservices is that they **work well for scenarios other than greenfield projects**.

- Choosing the **right migration strategy** is a complex task. It **depends on the legacy system and migration goals**. This chapter shows a starting point from which each project must develop its own strategy.

- Because of the benefits of migration, microservices should be considered in any project meant to modernize a legacy system. Microservices enable step-by-step modernization, in which completely different technologies can be used. This is very helpful.

- The **migration strategy can have a significant impact** on the architecture and technology selection. A split into microservices similar to the split of the modules in the legacy system can greatly simplify migration. Such a compromise has far-reaching consequences and can lead to a worse target architecture,
but it can still make sense.

- Finally, it must be possible to actually implement the architecture, and for this, a simple approach for the migration into the architecture is essential.

In this lesson, we'll formally conclude this chapter with some notes regarding migration.

Microservices

Micro and Macro Architecture

Migration

Docker

Technical Micro Architecture

Appendix

Conclusion

Chapter Conclusion

Summary #