28,772 views
In the early stages of developing microservice solutions, you usually don’t think about the challenges you’ll face. At some point after the release, there usually arises a need to increase reliability, improve scalability, reduce response time, and divide responsibility between teams. However, the solution may not be ready for this. Microservices are not a new architecture, and over the course of its existence, it has already acquired typical solutions - patterns. We’ll talk about patterns today. What’s on the agenda: * Patterns for decomposing a monolith into microservices. * Patterns for increasing the reliability of synchronous and asynchronous interaction. * Patterns for observability and organizing a public API.