Please enable JavaScript.
Coggle requires JavaScript to display documents.
M2M - Coggle Diagram
M2M
Chapter 4: Decomposing the Database
Pattern: The Shared Database
Pattern: Database view
Pattern: Database Wrapping Service
Pattern: Database as a service interface
Transferring Ownership
Data Synchronization
Pattern: Synchronize Data in Application
Pattern: Tracer Write
Splitting Apart the Database
Splitting the Database First, or the Code ?
Pattern: Split Table
12: Pattern: Move Foreign-Key relationship to Code
Transactions
Sagas
Chapter 2: Planning a Migration
Understanding the Goal
Why might you choose Microservice?
When might microservices be a bad idea ?
Trade-offs ?
Taking People on the Journey
Changing Organizations
Importance of Incremental Migration
Cost of Change
Where do we start ?
DDD
A combined model
Reorganizing Teams
How will you know if the transition is working ?
Chapter 5: Growing Pains
More services, more pain
Ownership at Scale
Breaking Changes
Reporting
Monitoring and Troubleshooting
Local Developer Experiences
Running Too Many Things
End-toEnd Testing
Global Versus Local Optimization
Robustness and Resiliency
Orphaned Services
Chapter 3: Splitting the Monolith
To change the Monolith, or Not ?
Pattern: Strangler Fig Application
Changing behavior while migrating functionality
Pattern: UI Composition
Pattern: Branch by Abstraction
Pattern: Parallel Run
Pattern: Decorating Collaborator
Pattern: Change Data Capture
Chapter 1: Just Enough Microservices
What are microservices?
Independently Deployable
Modeled Around a Business Domain
Own Their Own Data
Advantage
Flexibility
Focus
Developers are esier to work in parallel
Disadvantage
Latency
Transaction
The monolith
On Coupling and Cohension
Just Enough DDD