Most new applications do not need to be microservices from the very beginning. It is faster, easier, and cheaper to start as a monolith and switch to microservices later if needed.
Over time, as monolith applications become less maintainable, some teams decide that the only way to solve the problem is to start refactoring by breaking their application into microservices.
Before going into microservices migration, it's crucial to carefully consider all the pros and cons and ensure you've reached your current monolith architecture limits.
If you don't have modules, I strongly recommend you consider them. They can provide many advantages without changing your architecture to microservices.
Collection
[
|
...
]