Book
マイクロサービスパターン
Microservices Patterns
Chris Richardson
Summary
Sagaパターン、CQRS、イベントソーシングなど、分散システム特有の トランザクション管理と非同期メッセージングの実装手法を詳解する上級書。
Target Readers
- マイクロサービスの実装パターンを学びたいアーキテクト
- 分散トランザクション管理に取り組むエンジニア
Tags
Colophon
- Publisher
- インプレス
- ISBN
- 978-4295008583
- Published
- Mar 2020
- List price
- ¥5,280incl. taxMay differ from the actual selling price on Amazon
Get this book
* The link above is an advertisement via Amazon Associates.Related Books
Prerequisites
- Recommended
Concurrency in Go
Concurrency in Go
Katherine Cox-Buday
Reason: Having understood concurrency within a single process, you extend to a world where multiple processes—services—coordinate asynchronously. Microservices Patterns provides coordination patterns for distributed systems—messaging, sagas, event-driven design—extending the idea of concurrency across the network.
- Recommended
Monolith to Microservices
Sam Newman
Reason: Once you can decide whether to split a monolith, you stock up on the implementation patterns needed after the split. Microservices Patterns catalogs the established practices for service decomposition, data management, communication, and deployment, bridging from 'how to divide' to 'how to build.'
- Recommended
Clean Architecture
Robert C. Martin
Reason: Once you can design boundaries and dependencies within a single process, you scale those principles to distributed systems. Microservices Patterns gives you the vocabulary for designing inter-service communication, consistency, and failure handling while preserving each service's internal architecture.
Next Books
- Recommended
Release It!, 2nd Edition
Design and Deploy Production-Ready Software
Michael T. Nygard
Reason: Once you can implement distributed systems, designing 'how they behave when they break' becomes essential. Release It! provides stability patterns like circuit breakers and bulkheads, teaching you to design systems where failures don't cascade.
- Recommended
Designing Data-Intensive Applications
Martin Kleppmann
Reason: Learning microservice implementation patterns, you inevitably hit the hard problem of keeping data consistent across services. Designing Data-Intensive Applications supplies the theory of distributed-data consistency, replication, and transactions, underpinning why those patterns work.
- Related
Web APIテスト技法
Testing Web APIs
Mark Winteringham
Reason: Splitting into services creates the risk that integrations break whenever an inter-service interface changes. Testing Web APIs provides a contract-testing strategy including consumer-driven contracts (CDC), weaving a verification net that keeps independent deployment safe.