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.
27. Preparing to Split
● Identify Current
Interactions
● Write Tests and
Monitors
● The Service’s
Contract (API +
SLA)
● Ensure Tests
and Monitors
Match App
28. Preparing to Split
● Identify Current
Interactions
● Write Tests and
Monitors
● The Service’s
Contract (API +
SLA)
● Ensure Tests
and Monitors
Match App
29. Preparing to Split
● Identify Current
Interactions
● Write Tests and
Monitors
● The Service’s
Contract (API +
SLA)
● Ensure Tests
and Monitors
Match App
30. Preparing to Split
● Identify Current
Interactions
● Write Tests and
Monitors
● The Service’s
Contract (API +
SLA)
● Ensure Tests
and Monitors
Match App
32. Breaking Off Chunks
● Start with
Peripheral
Services
● Minimize
Dependencies
on Monolith
● Don’t be afraid
of Macro
Services
● Prioritize for
team velocity
33. Breaking Off Chunks
● Start with
Peripheral
Services
● Minimize
Dependencies
on Monolith
● Don’t be afraid
of Macro
Services
● Prioritize for
team velocity
34. Breaking Off Chunks
● Start with
Peripheral
Services
● Minimize
Dependencies
on Monolith
● Don’t be afraid
of Macro
Services
● Prioritize for
team velocity
35. Breaking Off Chunks
● Start with
Peripheral
Services
● Minimize
Dependencies
on Monolith
● Don’t be afraid
of Macro
Services
● Prioritize for
team velocity