Uploaded byAtlassian
Your Journey to Cloud-Native Begins with DevOps, Microservices, and Containers
The document discusses the journey to cloud-native architecture, emphasizing the significance of DevOps, microservices, and containers in enhancing digital agility and innovation. It outlines key concepts, including the transition from monolithic to modular applications, the role of automation through tools like Docker and Kubernetes, and the necessity of a CI/CD pipeline for rapid deployment and recovery. Additionally, it highlights the importance of modern monitoring strategies and the benefits of adopting a microservices architecture to improve scalability and fault isolation.
More Related Content
Similar to Your Journey to Cloud-Native Begins with DevOps, Microservices, and Containers
![Getting Started with Apache Spark: Big Data Made Simple [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/apachesparkgettingstarted-260203175547-8361bcc3-thumbnail.jpg?width=640&height=640&fit=bounds)
Your Journey to Cloud-Native Begins with DevOps, Microservices, and Containers
- 1. Your Journey To CloudNative: DevOps, Microservices and Containers MIKE MAHEU | GO2GROUP | @GO2GROUP
- 2. The destination is thesame. We are just taking a faster route. INTRODUCTION
- 3. Agenda The Journey Cloud Native DevOps MicroserviceArchitecture Containers Putting it Together
- 4. What are weleaving behind? AN EVOLUTIONARY JOURNEY
- 5. Microservices Break up thosedata structures Three Things We’ll Need for Cloud-Native Containers Docker and Kubernetes DevOps Same drill with some new bits
- 6. “Digitally advanced enterprises are8x more likely to grow share but still lag behind digital natives.” Bain Survey: For Traditional Enterprises, the Path to Digital and the Role of Containers
- 7. Disrupted Business Models? Switchingto a culture of organizational agility that can be flexible while maintaining a face pace. Digital Innovation Today Mobile devices, wearables, AI, Chatbots, Blockchain, and Machine Learning. Speed: A must have to do digital business today
- 8. Agenda The Journey Cloud Native DevOps MicroserviceArchitecture Containers Putting it Together
- 9. Cloud-native architecture is builtfor running in the cloud. CLOUD NATIVE
- 10. Cloud-native is abouthow applications are created and deployed not where they are going BEING CLOUD NATIVE
- 11. Cloud- Native Languages Automation Modular Stateless Languages for thecloud • HTML • CSS • Java • Javascript • .Net • Go • Node.js • PHP • Python • Ruby
- 12. Cloud- Native Languages Automation Modular Stateless Automated Cloud-Native Delivery: 1. Cloud-nativeapplications are automated 2. They need 1. Reliable 2. Repeatable 3. Proven 4. Known working processes 3. Require orchestration and automation tooling
- 13. Cloud- Native Languages Automation Modular Stateless On-Premise applications tendto be Monolithic 1. Cloud-native applications are modular 2. Functionality is broken down into Microservices that represent business functionality.
- 14. Cloud- Native Languages Automation Modular Stateless Loosely Coupled 1. Theloosely coupled nature of the cloud enables applications to not be tied to infrastructure which makes them stateless. 2.On-premise applications are stateful and rely on their state being maintained on the infrastructure they are being run on
- 15. Auto- Provisioning Architectural Runway Elastic Auto Scaling Auto Redundancy Minimize Failure Precision Knownand expected Results Key Benefits
- 16. Agenda The Journey DevOps Cloud Native MicroserviceArchitecture Containers Putting it Together
- 17. Within a yearof Amazon’s move to AWS, engineers deploying code every 11.7 seconds, on average. CHRISTOPHER NULL, TECH TRAIL BLAZERS
- 18. DevOps is culture,practices, and tooling that supports the ability to deliver applications at high velocity.
- 19. Cloud-Native DevOps Infrastructure asCode (IaC) Is the process of managing and provisioning computer data centers through machine-readable definition files. YAML Monitoring and Logging Cloud Native applications require a different monitoring approach. One that can include: external polling, centralized logging, metrics, and request tracking. CI / CD Continuous Integration and Continuous Deployment are the backbone of the modern DevOps environment Microservices In a micro services architecture, services are fine-grained and the protocols are lightweight
- 20.
- 21. Teams focus oncode and live in Git.
- 22. Pipelines • A perfectmodel for secure, cloud native CI/CD pipelines • Fast times to deployment and recovery Monitoring Streamlined approach to managing and observing applications with modern monitoring frameworks. Rollback Stable and reproducible rollbacks ie. revert, fork GitOps is Continuous Delivery meets Cloud Native
- 23. Rollback Stable and reproduciblerollbacks ie. revert, fork Monitoring Streamlined approach to managing and observing applications with modern monitoring frameworks. Pipelines • A perfect model for secure, cloud native CI/CD pipelines • Fast times to deployment and recovery GitOps is Continuous Delivery meets Cloud Native
- 24. Monitoring Streamlined approach tomanaging and observing applications with modern monitoring frameworks. Rollback Stable and reproducible rollbacks ie. revert, fork Pipelines • A perfect model for secure, cloud native CI/CD pipelines • Fast times to deployment and recovery GitOps is Continuous Delivery meets Cloud Native
- 25. Agenda The Journey Microservice Architecture CloudNative DevOps Containers Putting it Together
- 26. In 2008 whenNetflix was still operating as a monolith, a single semicolon brought down the entire Netflix website. Why You Can’t Talk About Microservices Without Mentioning Netflix
- 27.
- 28.
- 29. APACHEBROWSER MYSQL DATABASE Inventory Service Shipping Service WarFile Store Front UI Accounting Service Tomcat MONOLITH Traditional web application architecture using MVC design pattern.
- 30. MOBILE BROWSER INVENTORY DATABASE Inventory Service Shipping Service REST API StoreFront Web App Accounting Service Tomcat ACCOUNTING DATABASE SHIPPING DATABASE API Gateway MICROSERVICE Microservice architecture
- 31. Divide and conquer.Split up those data structures DATA STRUCTURES
- 32. Plan how yourapplication will behave if one service is down. PLAN
- 33.
- 34. No Vendor Lock-In Occurswhen a customer becomes dependent on a vendor for products and services. It can be caused by technical dependencies. Fault Isolation The practice of designing systems that limit negative consequences when bad things happen. Clarity Smaller more focussed services allow teams to focus on more clear and precise requirements. The requirements are specific to their speciality services.
- 35. Agenda The Journey Containers Cloud Native DevOps MicroserviceAchitecture Whats Next?
- 36. Containers everything at Google runsin containers
- 37. Containers Benefits Complexity Containers Benefits 1. Welldefined, isolated runtime environments 2. Packaging by Docker files p 3. Promotion through a CI/CD pipeline 4. Fast provisioning 5. Fast spin up 6. Development to Production 7. Scaling
- 38. Containers Benefits Complexity Deployment complexity increases. • AContainer must be deployed many times throughout the pipeline. • With so many services needing to be deployed independently, the number of deployments increases dramatically. • Monitoring and logging becomes more complex based on the increased number of moving parts and different distributed services.
- 39. Kubernetes a container orchestration systemfor automating containerized application deployments
- 40. Containerize an applications bycreating Docker config files and build processes to produce all the necessary Docker images Monitoring If you don’t need any of the points, don’t use them. We don’t believe in filler, baby! Kubernetes to manage deploying , scaling, and updating your applications Orchestrate and monitor those containers like a boss
- 41. Kubernetes to manage deploying,scaling, and updating your applications Monitoring If you don’t need any of the points, don’t use them. We don’t believe in filler, baby! Containerize An applications by creating Docker config files and build processes to produce all the necessary Docker images Orchestrate and monitor those containers like a boss
- 42. Monitoring monitor application performancein a K8s cluster by examining containers, pods, and services Kubernetes to manage deploying , scaling, and updating applications Containerize an applications by creating Docker config files and build processes to produce all the necessary Docker images Orchestrate and monitor those containers like a boss
- 43. One more thing PuttingIt All Together
- 44. Isolated CLOUD NATIVE INGREDIENTS CONTAINERS MICROSERVICES CloudAgile Governance DEVOPS
- 45. Thank you! We knowthat was a lot ;)