Cover
Half Title
Title Page
Copyright Page
Contents
Foreword
Preface
Acknowledgments
About the Authors
Part I: Transformational Strategic Learning through Experimentation
Executive Summary
Chapter 1: Business Goals and Digital Transformation
Digital Transformation: What Is the Goal?
Software Architecture Quick Glance
Why Software Goes Wrong
Debt Metaphor
Software Entropy
Big Ball of Mud
Running Example
Your Enterprise and Conwayโs Law
Communication Is about Knowledge
The Telephone Game
Reaching Agreement Is Hard
But Not Impossible
(Re)Thinking Software Strategy
Thinking
Rethinking
Are Monoliths Bad?
Are Microservices Good?
Donโt Blame Agile
Getting Unstuck
Summary
References
Chapter 2: Essential Strategic Learning Tools
Making Decisions Early and Late, Right and Wrong
Culture and Teams
Failure Is Not Fatal
Failure Culture Is Not Blame Culture
Enabling Safe Experimentations
Getting Conwayโs Law Right
Modules First
Deployment Last
Everything in Between
Business Capabilities, Business Processes, and Strategic Goals
Strategic Delivery on Purpose
Using Cynefin to Make Decisions
Where Is Your Spaghetti and How Fast Does It Cook?
Strategic Architecture
Applying the Tools
Summary
References
Chapter 3: Events-First Experimentation and Discovery
Commands and Events
Using Software Models
Rapid Learning with EventStorming
When Remote Sessions Are Demanded
Facilitating Sessions
Big-Picture Modeling
Applying the Tools
Summary
References
Part II: Driving Business Innovation
Executive Summary
Chapter 4: Reaching Domain-Driven Results
Domains and Subdomains
Summary
References
Chapter 5: Contextual Expertise
Bounded Context and Ubiquitous Language
Core Domain
Supporting Subdomains, Generic Subdomains, and Technical Mechanisms
Supporting Subdomains
Generic Subdomains
Technical Mechanisms
Business Capabilities and Contexts
Not Too Big, Not Too Small
Summary
References
Chapter 6: Mapping, Failing, and SucceedingโChoose Two
Context Mapping
Partnership
Shared Kernel
CustomerโSupplier Development
Conformist
Anticorruption Layer
Open-Host Service
Published Language
Separate Ways
Topography Modeling
Ways to Fail and Succeed
Applying the Tools
Summary
References
Chapter 7: Modeling Domain Concepts
Entities
Value Objects
Domain Services
Aggregates
Functional Behavior
Applying the Tools
Summary
References
Part III: Events-First Architecture
Executive Summary
Chapter 8: Foundation Architecture
Architectural Styles, Patterns, and Decision Drivers
Ports and Adapters (Hexagonal)
Modularization
REST RequestโResponse
Quality Attributes
Security
Privacy
Performance
Scalability
Resilience: Reliability and Fault Tolerance
Complexity
Applying the Tools
Summary
References
Chapter 9: Message- and Event-Driven Architectures
Message- and Event-Based REST
Event Logs
Subscriber Polling
Server-Sent Events
Event-Driven and Process Management
Event Sourcing
CQRS
Serverless and Function as a Service
Applying the Tools
Summary
References
Part IV: The Two Paths for Purposeful Architecture
Executive Summary
Chapter 10: Building Monoliths Like You Mean It
Historical Perspective
Right from the Start
Business Capabilities
Architecture Decisions
Right from Wrong
Change within Change
Break the Coupling
Keeping It Right
Summary
References
Chapter 11: Monolith to Microservices Like a Boss
Mental Preparation with Resolve
Modular Monolith to Microservices
Big Ball of Mud Monolith to Microservices
User Interactions
Harmonizing Data Changes
Deciding What to Strangle
Unplugging the Legacy Monolith
Summary
References
Chapter 12: Require Balance, Demand Strategy
Balance and Quality Attributes
Strategy and Purpose
Business Goals Inform Digital Transformation
Use Strategic Learning Tools
Event-Driven Lightweight Modeling
Driving Business Innovation
Events-First Architecture
Monoliths as a First-Order Concern
Purposeful Microservices from a Monolith
Balance Is Unbiased, Innovation Is Essential
Conclusion
References
Index
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
T
U
V
W
Y
Z