Working in the software development industry, I often see articles on monolith pros and cons, microservices pros and cons, monolith vs. microservices, etc. — and much less often about the correct transitions between architectural approaches and their interactions. While projects can grow rapidly or dramatically change their course of development, you need to know when and what architectural approach will help support the system.
This article is for those for whom the monolith hasn’t solved problems and only aggravates all processes. It will also come in handy for those who are just getting acquainted with microservices. I will not say which is better, but I will share my experience of migrating from a monolithic to a microservice architecture.