Monolithic code bases are not only difficult to maintain, they slow your development teams. As your application grows, the tight coupling of code and teams can bring progress to a halt. In this session, Datadog shares tips for uncoupling your teams and breaking large code bases into microservices. This presentation is brought to you by AWS partner, Datadog.

1. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.S U M M I T
Breaking Down Monoliths
H. “Waldo” Grunenwald
Tech Evangelist
Datadog
S e s s i o n I D

2. Breaking Down Monoliths

3. H. “Waldo” Grunenwald
Tech Evangelist
Datadog
Breaking Down Monoliths

4. Your Story

6. @gwaldo
Tech Evangelist & Writer
“Docs & Talks”
Recovering Ops Engineer

7. @datadoghq
SaaS-based monitoring
250+ integrations
Trillions of data points per day
https://datadoghq.com

8. What do you mean by “Microservices”?

9. You might be a Microservice if...
● Abstracted
● Reusable
● Autonomous
● Stateless
● Discoverable
● Composable

10. You might be a Microservice if...
● Abstracted
● Reusable
● Autonomous
● Stateless
● Discoverable
● Composable

11. You might be a Microservice if...
● Abstracted
● Reusable
● Autonomous
● Stateless
● Discoverable
● Composable

12. You might be a Microservice if...
● Abstracted
● Reusable
● Autonomous
● Stateless
● Discoverable
● Composable

13. You might be a Microservice if...
● Abstracted
● Reusable
● Autonomous
● Stateless
● Discoverable
● Composable

14. You might be a Microservice if...
● Abstracted
● Reusable
● Autonomous
● Stateless
● Discoverable
● Composable

15. There is no real definition

16. Why Microservices?

17. Why…?
● Loose Coupling
● Greater Agility
● Faster to Market
● Better
Scalability
● Better Fault
Tolerance
● Platform &
Language
Agnostic
● Cloud-Ready

18. Why…?
● Loose Coupling
● Greater Agility
● Faster to Market
● Better
Scalability
● Better Fault
Tolerance
● Platform &
Language
Agnostic
● Cloud-Ready

19. Why…?
● Loose Coupling
● Greater Agility
● Faster to Market
● Better
Scalability
● Better Fault
Tolerance
● Platform &
Language
Agnostic
● Cloud-Ready

20. Why…?
● Loose Coupling
● Greater Agility
● Faster to Market
● Better
Scalability
● Better Fault
Tolerance
● Platform &
Language
Agnostic
● Cloud-Ready

21. Why…?
● Loose Coupling
● Greater Agility
● Faster to Market
● Better
Scalability
● Better Fault
Tolerance
● Platform &
Language
Agnostic
● Cloud-Ready

22. Why…?
● Loose Coupling
● Greater Agility
● Faster to Market
● Better
Scalability
● Better Fault
Tolerance
● Platform &
Language
Agnostic
● Cloud-Ready

23. Why…?
● Loose Coupling
● Greater Agility
● Faster to Market
● Better
Scalability
● Better Fault
Tolerance
● Platform &
Language
Agnostic
● Cloud-Ready

24. How to go about breaking apart code?

25. Identify Products

28. The Sandi Metz Rule

29. The Sandi Metz Rule

30. Preparing to Split

31. Preparing to Split
● Identify Current
Interactions
● Write Tests and
Monitors
● The Service’s
Contract (API +
SLA)
● Ensure Tests
and Monitors
Match App

32. Preparing to Split
● Identify Current
Interactions
● Write Tests and
Monitors
● The Service’s
Contract (API +
SLA)
● Ensure Tests
and Monitors
Match App

33. Preparing to Split
● Identify Current
Interactions
● Write Tests and
Monitors
● The Service’s
Contract (API +
SLA)
● Ensure Tests
and Monitors
Match App

34. Preparing to Split
● Identify Current
Interactions
● Write Tests and
Monitors
● The Service’s
Contract (API +
SLA)
● Ensure Tests
and Monitors
Match App

35. Breaking Off Chunks

36. Breaking Off Chunks
● Start with
Peripheral
Services
● Minimize
Dependencies
on Monolith
● Don’t be afraid
of Macro
Services
● Prioritize for
team velocity

37. Breaking Off Chunks
● Start with
Peripheral
Services
● Minimize
Dependencies
on Monolith
● Don’t be afraid
of Macro
Services
● Prioritize for
team velocity

38. Breaking Off Chunks
● Start with
Peripheral
Services
● Minimize
Dependencies
on Monolith
● Don’t be afraid
of Macro
Services
● Prioritize for
team velocity

39. Breaking Off Chunks
● Start with
Peripheral
Services
● Minimize
Dependencies
on Monolith
● Don’t be afraid
of Macro
Services
● Prioritize for
team velocity

40. Breaking Off Chunks
● Start with
Peripheral
Services
● Minimize
Dependencies
on Monolith
● Don’t be afraid
of Macro
Services
● Prioritize for
team velocity

41. Moving to Product-
Oriented Teams

42. Project vs. Product,
and Funding Models

43. Project vs. Product,
and Funding Models

44. Charter the Product Team

45. Breaking Down Monoliths:
Conclusion
H. “Waldo” Grunenwald
Tech Evangelist
Datadog

46. Visit Our Booth

47. Thank you!
S U M M I T © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
H. “Waldo” Grunenwald
waldo@datadoghq.com
@gwaldo