Common principles of breaking down a Monolith into Microservices
#monolith #microservices #architecture
• Define schema domains that are presented in the database. Put unrelated tables into separate categories — each category is a potential microservice. You will also need to break up queries into multiple simple queries that are merged at the application level.
• Second step would be to separate functional blocks out of a highly coupled modules. Start with core features and then work the way out with optional features.
• Make those services that don't require to be synchronous to be event-driven. Apply common patterns like two-phase transactions, circuit breaker and backoff retry.
• Outline common observability and security dependencies for all future microservices and create an out-of-the-box template for future generations of developers.
infoq.com/presentations/github-rails-monolith-microservices/
