Downloaded 11 times
Uploaded byLuiz Fernando Signorelli
Microservices architecture
Microservices architecture structures applications as a collection of loosely coupled services, enhancing autonomous team workflows and service scalability. While it offers benefits like independent deployment and better fault isolation, it also introduces complexities such as service management and testing. The document outlines prerequisites for adopting microservices and discusses the importance of service meshes in managing service communication.
More Related Content
Similar to Microservices architecture
Microservices architecture
- 1. Microservices Architecture Luiz FernandoSignorelli
- 2.
- 3. “Microservices - alsoknown as the microservice architecture - is an architectural style that structures an application as a collection of loosely coupled services, which implement business capabilities” - microservices.io
- 4. “In short, themicroservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery” - Martin Fowler
- 5. “Microservices is avariant of the service-oriented architecture (SOA) architectural style that structures an application as a collection of loosely coupled services” - Wikipedia
- 6.
- 7.
- 8.
- 9. Benefits of theMonolith ● Easy to start ● Easy to understand ● Communication between modules ● Simple to change ● Easy to test ● Good for small teams ● Simple to scale
- 10. Drawbacks of theMonolith ● It grows! ● Too big to fit on someone's head ● Deploy becomes challenging ● Simple to change ● Bad for big teams ● Reliability ● Difficult to change the technology stack
- 11. Microservices to therescue
- 12. Benefits of Microservices ●Enables teams to be autonomous ● Each service is a small, maintainable application ● Services are independently deployable ● Services are independently scalable ● Easier to adopt new technologies ● Improved fault isolation
- 13. Drawbacks of Microservices ●Deciding when to adopt ● How to break down services ● Distributed systems are complex ● Deploying requires careful coordination ● Testing the whole thing is difficult ● Operations
- 14. CAP Theorem If yoursystem can have a network partition you have to choose between consistency and availability. The choice boils down to a business decision.
- 15. Don't!First Law ofDistributed Object Design
- 16.
- 17.
- 18.
- 19. Calçados's Microservices Prerequisites 1. Rapid provisioningof compute resources 2. Basic monitoring 3. Rapid deployment 4. Easy to provision storage 5. Easy access to the edge 6. Authentication/Authorisation 7. Standardised RPC
- 20. Event Sourcing andCQRS ● Greg Young ● The event log as the source of truth ● Enables async communication ● Automatic Audit
- 21.
- 22. Service Mesh ● Centrallog ● Central configuration ● Circuit breaker ● Routing ● Service discovery, ● Tracing ● Metrics ● Linkerd ● Conduit ● Envoy ● Istio
- 23. “A service meshis a dedicated infrastructure layer for handling service-to-service communication. It’s responsible for the reliable delivery of requests through the complex topology of services that comprise a modern, cloud native application. In practice, the service mesh is typically implemented as an array of lightweight network proxies that are deployed alongside application code, without the application needing to be aware.” - William Morgan, boyant.io
- 24.
- 25.