Download as PDF, PPTX
Uploaded byEberhard Wolff
Microservices, DevOps, Continuous Delivery – More Than Three Buzzwords
This document discusses how microservices, continuous delivery, and DevOps relate and solve problems together. Microservices break applications into independently deployable components, continuous delivery incorporates automated testing and deployment pipelines, and DevOps emphasizes collaboration between development and operations teams. Together, these approaches enable faster and more reliable software releases by allowing components to be deployed independently while maintaining overall system integrity through practices like monitoring and common infrastructure standards. They also allow alternative approaches to challenges like maintainability and scalability by facilitating fast feedback loops and the ability to quickly identify and address bottlenecks.
More Related Content
Similar to Microservices, DevOps, Continuous Delivery – More Than Three Buzzwords
Microservices, DevOps, Continuous Delivery – More Than Three Buzzwords
- 1. Microservices, DevOps, Continuous Delivery– More Than Three Buzzwords Eberhard Wolff Fellow @ewolff
- 2. Microservices, DevOps, Continuous Delivery – HowDo They Relate?
- 3. Microservices, DevOps, Continuous Delivery – HowDo They Solve Problems?
- 5.
- 6.
- 7. UNIX Philosophy > Writeprograms that do one thing and do it well > Write programs to work together > Write programs with a common interface
- 8. Definition Microservice > Independent deploymentunit > Separate data handling & storage > Should include UI > Order process, Billing, Catalog… > Process > VM > Docker container Server Micro Service
- 9. Deployment Monolith > Mightbe well-structured inside. > But: Can only be deployed as a whole
- 10. Continuous Delivery: Build Pipeline Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing Release DeployDeploy Deploy Deploy Automated Reproducible Fast
- 11.
- 12. Continuous Delivery Pipeline toocomplex or slow?
- 13. Continuous Delivery Pipeline toocomplex or slow? Consider changing the architecture!
- 14. Microservices: Challenges > 50 or100 Microservices > Deployment? > Monitoring? > Log Analysis? > Need Automation > Need common foundation for operations > Small deployment units are not enough
- 15. Continuous Delivery Pipeline Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing Release Integration Test Microservice CompleteSystem Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing
- 16.
- 17. Microservices can only bedeployed independently if tests are independent!
- 18. Microservices can only bedeployed independently if your Continuous Delivery Pipeline works.
- 19.
- 20. Why all thehassle?
- 21. Conway‘s Law Architecture copies communication structures ofthe organization
- 22. Conway’s Law asa Limit > Organization drives architecture > Teams of experts > i.e. UI, logic & database team > Three technical artifacts
- 23.
- 24. time DB Team Sprint Logic Team Sprint GUI TeamSprint 3 sprints
- 25. Order SearchBilling Team foreach business feature Let architecture drive the organization Order Billing Search
- 26. Deployment Monolith + Conway’sLaw Deployment Monolith Stories Technical Coordination Coordinating Releases StoriesStories Order Billing Search
- 27. Team can deploywithout integration Changes can be deployed independently & quickly Strong & enforced modularization Technology stack per Microservice One or many Microservices per Team Synergy Microservices / Conway’s Law Order SearchBilling Order Billing Search
- 28.
- 29. Microservices: Challenges > Deployment? > Monitoring? >Log Analysis? Ops
- 30.
- 31. Macro-Architecture > Global decision >Influence the whole system > i.e. all Microservices > Less Marco-Architecture – less coordination
- 32. Micro-Architecture > Local decisions >Per Microservice
- 33. Macro- and Micro- Architecturefor Ops > Macro > Define Log Analysis, Monitoring, Deployment tools > Defined globally > Micro > Concrete deployment, monitoring, logging > Defined per team / Microservice
- 34. Microservices Teams need manytechnical skills.
- 35.
- 36.
- 37. DevOps / Microservices > Teamsconsist primarily of Devs > Devs interested in Docker, ELK ... > ... lots of experience in Ops > More Ops effort
- 38. Microservices = huge opportunityfor Ops!
- 39. How Much DevOpsis Needed? > Should all teams do full ops for their services? > IMHO optional > But: Organizational barriers might cause additional technical complexity
- 40. Continuous Delivery: Build Pipeline Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing Release DevOps Common Technologies Log, Monitoring, Deployment
- 41.
- 42.
- 43.
- 44. Maintainability: Classical Approach > Cleararchitecture > Good code quality > Many tests Dev
- 45.
- 46. Maintainibility: New Approach > ContinuousDelivery simplifies roll out > ...and test them > ...and monitor them > Microservices limit size and risk of changes DevOps
- 47.
- 48. Scalabilty: Classical Approach > Implementtechnical constraints > E.g. statelessness > Use appropiate technologies Dev
- 49. Performance Risk > Hardto really predict performance > Load test simulate user on a different environment
- 50. Scalability: Alternative Approach > Don‘tdo anything stupid in the architecture > Identify bottleneck > Eliminate bottleneck > Common technique
- 51. Enable Alternative Approach > Monitoringto identify bottleneck > Fast deployment to eliminate bottleneck DevOps
- 52.
- 53.
- 54. Conclusion > Synergy: Microservices andContinuous Delivery > Microservices and Continuous Delivery support and require DevOps > DevOps = Collaboration > Enable alternative approaches e.g. to maintainability and scalability
- 55.