The document discusses the key components of microservices including technology, process, and people. It describes microservices as service-oriented development where software is developed through an iterative process of incremental improvements and checks. This process relies on tools for quick deployment, observability to measure impact, and resilience to prevent failures from cascading. The technology aspects provide scaffolding to support this development approach including options for resource orchestration, traffic management, and example implementation choices.

1. Microservices: move fast and
break make things
(topologies of business logic)
Rafael Schloming
CTO

2. datawire.io
Three components of Microservices
2
Technology
Process
People

3. datawire.io
Process
3

4. datawire.io
Microservices: Service Oriented Development
What this means
Why it works
How to do it
4

5. datawire.io
Architecture vs Development
5

6. datawire.io
Engineering is Guess & Check
6

7. datawire.io
Cost of Guess/Check
7

8. datawire.io
Cost of Guess/Check
8
ModernDevelopment
PunchCards
Moore’s Law

9. datawire.io
Cost of Guess/Check
9
ServiceO.Development
ServiceO.Architecture
Cloud

10. datawire.io
Software vs SaaS
10
VS

11. datawire.io
Microservices is Service Oriented Development
The output of the process:
● Continuously improving Software as a Service
The process:
● Guess (incremental improvements)
● Check (both functionality and health)
The tools:
● Deployment - make small guesses
● Observability - measure the impact on health
● Resilience - ensure negative health impacts are not catastrophic
11

12. datawire.io
People
12

13. datawire.io
Microservices: Architecture for Distributing Accountability
What this means
Why it works
How to do it
13

14. datawire.io
Cheap Guess/Check merges roles
14

15. datawire.io
Aggregate Health: Christmas Tree Lights
15
A B C D EX

16. datawire.io
Two Perspectives
C’s problem: Is it worth it? D’s problem: Did I break C?
16
C DX

17. datawire.io
Two Solutions
Operational Responsibility System Visibility & Resilience
17

18. datawire.io
Microservices is Service Oriented Development
The output of the process:
● Continuously improving Software as a Service
The process:
● Guess (incremental improvements)
● Check (functionality, individual health, overall toxicity)
The tools:
● Deployment - make small guesses
● Observability - measure the impact on individual health & overall toxicity
● Resilience - ensure negative impact is not catastrophic and doesn’t cascade
18

19. datawire.io
Technology
19

20. datawire.io
Microservices Technology: SoD Scaffolding
Requirements
Design
Implementation
20

21. datawire.io
Early (Small/Shallow Topologies)
Deployment
● Fast pipeline (minimum time from git -> cloud)
● Self service provisioning
Observability
● Service level metrics (throughput, latency, availability)
Resilience
● Incremental rollout
21

22. datawire.io
Later (Large/Deep Topologies)
Deployment
● Fast pipeline (minimum time from git -> cloud)
● Self service provisioning
Observability
● Service level metrics & logging (throughput, latency, availability)
● Trace level visibility (profiling, logging, stack traces)
Resilience
● Incremental rollout
● Timeouts, Deadlines, Retries, Budgets, Circuit Breakers, Rate Limiting
22

23. datawire.io
Microservices Scaffolding Design
Resource Orchestration:
● PaaS
● Cluster Managers (kubernetes and friends)
Traffic Management
● L7 Sidecar
● SDK
23

24. datawire.io
Example Implementation Options
Resource Orchestration
● Kubernetes, Mesos, AWS ECS, ...
Traffic Management (L7 Sidecar)
● Envoy, SmartStack, L8d, ...
Traffic Management (SDK)
● gRPC, finagle, ...
24

25. datawire.io
For more information...
Resources:
● https://www.datawire.io/guide
● https://www.microservices.com
● https://eng.lyft.com/announcing-envoy-c-l7-proxy-and-communication-bus-925
20b6c8191
● https://engineeringblog.yelp.com
Contact:
● rhs@datawire.io
25