Cloud Native Event-Driven Applications on LKE
1 like221 views
The document outlines a Linode webinar focused on developing cloud-native event-driven applications, particularly using tools like Kubernetes, Knative, and the Zeebe workflow engine. It emphasizes the importance of architecture, tooling, and best practices for handling high-demand scenarios, such as managing ticket sales with concurrent users and event orchestration. Key takeaways include the necessity for decoupled architectures and collaboration between technical and non-technical teams, as well as leveraging open-source communities.
Cloud Native Event-Driven Applications on LKE
- 1. 1 Cloud Native Event-Driven Applications done right Linode Webinar - 29/10/2020
- 2. 2 @Salaboy @Camunda / @ZeebeHQ / @LearnK8s http://salaboy.com Mauricio Salatino
- 3. 3
- 4. 4 Disclaimer Live, Remote, WebSockets, Kubernetes, Knative, Cloud Events, Docker, Java, my laptop, what can possibly go wrong?
- 5. 5 Once Upon a Time … Tickets Website Instructions/Source Code: https://github.com/salaboy/orchestrating-cloud-events/
- 6. 6 Considerations More Buyers than Actual Tickets Huge spike in demand at sale time Time Sensitive Reservations
- 7. 7 How would you go about implementing such system?
- 10. 10 Event-Driven
- 12. 12 Questions?
- 13. 13 Tooling
- 14. 14 > kubectl get nodes -owide
- 16. 16 Packaging and Dependency Management > helm list > helm repo list
- 17. 17 Knative Serving. Knative Eventing. Universal subscrip/on, delivery, and management of events. Run serverless containers on Kubernetes with ease, Kna/ve takes care of the details of networking, autoscaling (even to zero), and revision tracking. > kubectl get ksvc > kubectl get ns
- 18. 18 But what about Service to Service interactions and payload format?
- 21. 21 ➡ Standard Envelope for sharing events ➡ Quite simple spec, but quite useful ➡ Bindings for: ➡ HTTP, AMQP, KaLa , MQTT , NATS , Avro What? http://cloudevents.io
- 23. 23 Tickets Website (Knative) > kubectl get broker
- 24. 24 Tickets Website (Knative) > kubectl get triggers
- 25. 25 Now imagine.. 10 K Users at the same time 60 K messages floating around
- 26. 26 Questions?
- 27. 27 Value
- 28. 28 ➡The sequence of events maNer ➡How do you deal with changes in this sequence? ➡It is hard to see where things are at a given /me ➡It is hard to figure out what to do when things go wrong Is it working? How?
- 29. 29 Zeebe Workflow Engine • Microservices and Events Orchestration • Available as • SaaS (console.cloud.camunda.io) • On-Prem (helm.zeebe.io)@ZeebeHQ http://zeebe.io
- 30. 30 Tickets Website (Knative + Zeebe)
- 31. 31 Tickets Website (Knative + Zeebe)
- 32. 32 Tickets Website (Knative + Zeebe)
- 35. 35 Version 3: Workflow Orchestration
- 36. 36 Version 4: Workflow Orchestration
- 37. 37 Questions?
- 38. 38 Take Aways •Cloud Native Patterns are important, use them to choose wisely which tools do you adopt •Build decoupled architectures where each service/team can evolve independently •Make sure that you promote collaboration between technical and non-technical teams •Tap into Open Source communities for best practices
- 39. 39