Often migration to microservices is painful due to lack of documentation and the ultimate goal of achieving high standards. Here we will understand how we can start with breaking a monolith application into microservices. So let start first understanding the most naive pattern of microservices.
A shared data is a controversial pattern when we talk about microservices. It would certainly be considered an anti-pattern if we applied to greenfield application. However, it is the pattern that should be considered as a temporary pattern for the legacy applications that are in a transition phase.
The great concept behind this pattern is to same physical structure for data storage. This pattern can be used when there is some doubt about the structure of the data or when the communication layer between microservices is not well defined.
BREAKING THE MONOLITHIC APPLICATION INTO MICROSERVICES
It is important to know that at the beginning of the transition period, the impression is that we are in the maze without an end., and that it was a big mistake to start the migration process.
There are some steps that may seem somewhat unnecessary or irrelevant. However, without these steps, any migration project for microservices will fall badly.
- Defining priorities
- Setting Deadlines
- Define domains of the application
- Making experiments
- Define standards
- Create prototype
- Send to production.
References :
- https://www.google.com/books/edition/Microservice_Patterns_and_Best_Practices/oyZKDwAAQBAJ?hl=en&gbpv=1&printsec=frontcover
- https://www.oreilly.com/library/view/architectural-patterns/9781787287495/c2746ee1-5be1-4261-a603-7255034c1f34.xhtml
- My other articles on Microservices on Load Balancing, CQRS (Command Query Responsibility Segregation), Event Sourcing, and a few more.