Download to read offline
![Coded Agents – with UiPath SDK + LangGraph [Virtual Hands-on Workshop]](https://cdn.slidesharecdn.com/ss_thumbnails/codedagentsdeck-251215155422-5497c599-thumbnail.jpg?width=640&height=640&fit=bounds)
CloudNativeCon Stability in an Unstable World
- 1.
- 2. Ravi Lachhman Technical Evangelist Stabilityin an Unstable World @ravilach
- 3. What are wetalking about? Stability in an Unstable World #KubeCon @ravilach •Two concepts that are at odds in computer science •Why the rise in Cloud Native •Justifying all of this change
- 4. Indempotency + Ephmeralilty =Cloud Native Stability in an Unstable World #KubeCon @ravilach
- 5. Doughnut Dilemma Stability inan Unstable World #KubeCon @ravilach
- 6. Doughnut Dilemma Stability inan Unstable World #KubeCon @ravilach
- 7. Idempotence(ɪdɛmˈpoʊtəns/) Stability in anUnstable World #KubeCon @ravilach
- 8. Idempotence Stability in anUnstable World #KubeCon @ravilach
- 9. Idempotency Stability in anUnstable World #KubeCon @ravilach
- 10. Idempotency = Safety? Stabilityin an Unstable World #KubeCon @ravilach
- 11. Enterprise Integration Patterns Stabilityin an Unstable World #KubeCon @ravilach
- 12. Ephemeral (əˈfem(ə)rəl/) Stability inan Unstable World #KubeCon @ravilach
- 13. Ephemeral Stability in anUnstable World #KubeCon @ravilach
- 14. Cloud Native (kloud/ˈnādiv/) Stability in an Unstable World #KubeCon @ravilach
- 15. Scale Stability in anUnstable World #KubeCon @ravilach
- 16. Recreatable Stability in anUnstable World #KubeCon @ravilach
- 17. Software is Eating theWorld -Marc Andreesen Stability in an Unstable World #KubeCon @ravilach
- 18. Software Defined Stability inan Unstable World #KubeCon @ravilach
- 19. All Layers Stability inan Unstable World #KubeCon @ravilach
- 20. Networking Stability in anUnstable World #KubeCon @ravilach
- 21. Storage Stability in anUnstable World #KubeCon @ravilach
- 22. Choice Overload! Stability inan Unstable World #KubeCon @ravilach
- 23. Indempotency + Ephmeralilty +Observability = Cloud Native Stability in an Unstable World #KubeCon @ravilach
- 24. Observability Stability in anUnstable World #KubeCon @ravilach
- 25. Has to begood? Stability in an Unstable World #KubeCon @ravilach
- 26. KPI? Is theK for K8’s? Stability in an Unstable World #KubeCon @ravilach
- 27. We learned alittle more about: Stability in an Unstable World #KubeCon @ravilach •Idempotency, Ephemerality, and Observability •Software Define Everything •Need of a solution to justify business outcomes
- 28. Software is Feeding theWorld -Ravi Lachhman Stability in an Unstable World #KubeCon @ravilach
- 29.
Editor's Notes
- #2 The underpinnings of Cloud Native
- #3 Technical Evangelist at AppDynamics. Prior experience at Mesosphere, Red Hat, and IBM. Specialties include SQL and NoSQL DB corruptions and not being able to do CIDR calculations.
- #4 Shift into Containers Container Orchestrators Rise in Container Orchestrator SDKs
- #5 Short lived and consistent results is the world we live in today.
- #6 I just want TWO doughnuts We need resources to fulfill the request. This is pretty accurate. I know there is always one in this type of box until exhausted
- #7 Your resource manager will help with this. Valid request!
- #8 In mathematics and computer science, idempotence is a property in which no matter how many times you execute some operations, you achieve the same outcome
- #9 In mathematics and computer science, idempotence is a property in which no matter how many times you execute some operations, you achieve the same outcome
- #10 Does it matter which box you are really on?
- #11 Enterprise Integration Patterns. The book’s authors, Gregor Hohpe and Bobby Woolf, describe a lot of the system-to-system design patterns that we depend on today. In the case of the financial service client, the design pattern was Idempotent Receiver (Consumer).
- #12 Start talking about sequence right away. Enterprise Integration Patterns. The book’s authors, Gregor Hohpe and Bobby Woolf, describe a lot of the system-to-system design patterns that we depend on today. In the case of the financial service client, the design pattern was Idempotent Receiver (Consumer). Re-iterate this new world. That is idempotency! Same outcomes regardless of input.
- #13 Ephemerality is a concept of things being short-lived or transitory.
- #14 Ephemerality is a concept of things being short-lived or transitory.
- #15 Ephemerality is a concept of things being short-lived or transitory.
- #16 Scale helps us overcome more than one problem. Availability and performance.
- #17 Since infrastructure is ephemeral, have to be able to recreate quickly. To have both Idem and Emph, need to be recreatable. To have scale, you need to build and destroy quickly. To build, aka “recreate” infrastructure.
- #19 Marc Andreessen’s famous quote—“software is eating the world”—proves equally true in the Cloud Native space. The most prolific push for generic hardware has been led by public cloud vendors. Similar to enterprises making the move to x86, cloud vendors have been pushing to make all parts of their stack as generic as possible. In case of failure or expansion, vendors can swap a generic part in and out with ease.
- #20 Configuration control and consistency is moving down the stack: from application to application infrastructure, and now down to infrastructure. With advances in software-defined infrastructure (SDI), the trifecta of load-balancing, clustering and replication can be applied to multiple parts of the stack.
- #21 Service Mesh With the ever-widening adoption of the container networking interface (CNI), containerized applications can have a more consistent approach to network connectivity. For example, with Cisco Application Centric Infrastructure as a robust SDN platform, coupled with a service mesh, enterprises have a consistent and recreatable way of discovering and participating in services. AppDynamics can provide insight into this increasingly complex networking landscape as well.
- #22 Not long ago, storage in the cloud world was viewed as non-ephemeral. But as offerings, practices and architectures have begun to shift for some cloud storage products, there’s now a delineation between ephemeral and non-ephemeral storage. Although one of the pillars of a twelve-factor application is to run stateless processes, some sort of state needs to be written somewhere, and a popular place is to disk. Advances in software-defined storage (SDS), with projects such as Ceph and Gluster, provide object and file storage capabilities, respectively. Similar to the delineation of SDN and CNI, there is SDS and Container Storage Interface (CSI). For example, Portworx, a popular cloud-native storage vendor, coupled with commodity cloud or on-premises storage, allows for greater portability and storage consistency from the infrastructure to the container/application level.
- #23 Pire amount of choice! https://github.com/cncf/landscape
- #24 Idempotency + Ephemerality + Observability = Cloud Native Despite the inherent challenges with observability, insight into the system is crucial. Relating changes in ephemeral infrastructure to overall sentiment and KPIs can be a challenge as well. With AppDynamics, it’s much easier to validate and advance your investment in the software-defined world.
- #25 In control theory, observability is a measure of how well internal states of a system can be inferred from knowledge of its external outputs. What is observability? Given an output, how well did a system perform. Going back to FreeCodeCamp’s palindrome example, if a string is a palindrome, how efficient was the system in determining the string was a palindrome?
- #26 In control theory, observability is a measure of how well internal states of a system can be inferred from knowledge of its external outputs. Just because the doughnut is hot, doesn’t make the entire process good. Since that doughnut is so good, has to be perfect? Used to wait forever to get them fresh….
- #27 Despite the inherent challenges with observability, insight into the system is crucial. Relating changes in ephemeral infrastructure to overall sentiment and KPIs can be a challenge as well. With AppDynamics, it’s much easier to validate and advance your investment in the software-defined world.
- #28 Idempotency and Ephemerality Software Define Everything Need of a solution to justify business outcomes
- #29 With the generic hardware approach, a good amount of logic moves to the software stack. The rationale here is that if hardware is ephemeral, reconstituting the compute, storage, and even networking would be both seamless and consistent with software-defined storage and networking. Applying this to the public/hybrid cloud market, a software-driven solution that’s robust, scalable and portable becomes a core component of Cloud Native.