Microservices


Building Microservices: Designing Fine-Grained Systems
Microservice Patterns
Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith
Building Event-Driven Microservices: Leveraging Organizational Data at Scale
Spring Microservices in Action
Production-Ready Microservices: Building Standardized Systems Across an Engineering Organization
Microservices in Action
The Tao of Microservices
Strategic Monoliths and Microservices: Driving Innovation Using Purposeful Architecture
Domain-Driven Design: Tackling Complexity in the Heart of Software
Microservices From Design to Deployment
Bootstrapping Microservices with Docker, Kubernetes, and Terraform: A project-based guide
Practical Microservices: Build Event-Driven Architectures with Event Sourcing and CQRS
Distributed Tracing in Practice: Instrumenting, Analyzing, and Debugging Microservices
Microservice Architecture Aligning Principles, Practices, and Culture
Designing Data-Intensive Applications by Martin KleppmannRelease It! by Michael T. NygardMicroservices From Design to Deployment by Chris RichardsonBuilding Microservices by Sam NewmanPython Microservices Development by Tarek Ziadé
To learn Microservices
21 books — 4 voters
Designing Data-Intensive Applications by Martin KleppmannDistributed Systems For Fun and Profit by Mikito TakadaBuilding Microservices by Sam NewmanDistributed Systems by Andrew S. TanenbaumMicroservices From Design to Deployment by Chris Richardson
Scalable System Design Books
8 books — 7 voters


Resilience versus Robustness. Typically when we want to improve a system’s ability to avoid outages, handle failures gracefully when they occur and recover quickly when they happen, we often talk about resilience. (…) Robustness is the ability of a system that is able to react to expected variations, Resilience is having an organisation capable of adapting to things that have not been thought of, which could very well include creating a culture of experimentation through things like chaos engin ...more
Sam Newman, Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith

By breaking our application into individual, independently deployable processes, we open up a host of mechanisms to improve the robustness of our applications. By using microservices, we are able to implement a more robust architecture, because functionality is decomposed, that is, an impact in one area of functionality may not bring down the whole system, we also can focus our time and energy on those parts of the application that most require robustness, ensuring critical parts of our system r ...more
Sam Newman, Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith

More quotes...
To be deleted This group is for Software Professionals interested in Software Architecture and related technol…more
1 member, last active 4 years ago
Redapt Engineering Book Club
2 members, last active 8 years ago
The Software Architect Bookshelf This group is for Software Professionals interested in Software Architecture and related technol…more
72 members, last active 4 years ago