Microservices Process: Service Oriented Development
The output of the process:
● Continuously improving Service
The process:
● Guess (incremental improvements)● Check (correctness + availability & user impact in production)
The tools:
● Deployment - make small guesses● Observability - measure the impact on functionality, availability, users● Resilience - ensure negative impacts are not catastrophic
14
datawire.io
Microservices Process: Service Oriented Development
Ignore architecture, focus on release frequency
As soon as you have users, adjust your process to measure user impact
Recognize that stability vs progress is a fundamental tradeoff
● for a single service…
15
datawire.io
People
16
datawire.io
Microservices People: Autonomous Teams
What this means
Why it works
How to do it
17
datawire.io
Cheap Guess/Check merges roles
18
datawire.io
Aggregate Health: God’s Eye View Harmful
19
A B C D EX
datawire.io
Two Perspectives
C’s problem: Is it worth it? D’s problem: Did I break C?
20
C DX
datawire.io
Two Solutions
Operational Responsibility System Visibility & Resilience