This document discusses moving from a monolithic application architecture to microservices using Kubernetes, Jenkins X, and Zeebe. It highlights considerations when breaking apart a monolith like dependencies between services, workflows buried in code, and edge cases. Zeebe is presented as a way to orchestrate microservices with a scalable and low latency architecture. The key takeaways are to understand the Kubernetes ecosystem, optimize what to build versus integrate, and focus on business value.

1. 1
From Monolith to Kuberneteswith @JenkinsXIO & @ZeebeHQ

2. 2
@Salaboy
Mauricio Salatino
http://salaboy.com
@ZeebeHQ / @Camunda / @LearnK8s

3. 3

4. 4
Disclaimer
Live, Remote, Kubernetes, Google, Github,
WiFi, my laptop,
what can possibly go wrong?

5. 5
https://github.com/salaboy/demo-conference-monolith/

6. 6
Jenkins X
CI/CD for Kubernetes
Part of the http://cd.foundation

7. 7

8. 8

9. 9

10. 10

11. 11
https://github.com/salaboy?tab=repositories&q=demo-conference

12. 12

13. 13
✴Dependencies between Services
✴Flow buried in code
✴Time Based Constraints
✴Edge Cases and UnHappy Paths
✴Implementing queries / analytics
Considerations

14. 14
Orchestration with Zeebe
Microservices Orchestration
@ZeebeHQ / http://zeebe.io
•Super Scalable Architecture
•Low latency / High throughput

15. 15

16. 16

17. 17
✴ Understand Kubernetes Ecosystem
✴ Optimize decisions around what to build and
what to integrate
✴ Focus on business value
Takeaways
Questions?