Microservices, DevOps, Continuous Delivery – More Than Three Buzzwords

Microservices, DevOps and Continuous Delivery are three hypes at the moment. This talk looks into the relationships between these three approaches and gives an idea how these approaches help to solve concrete problems. Held at Continuous Lifecycle 2015.

1. Microservices, DevOps, Continuous Delivery – More Than Three Buzzwords Eberhard Wolff Fellow @ewolff
2. Microservices, DevOps, Continuous Delivery – How Do They Relate?
3. Microservices, DevOps, Continuous Delivery – How Do They Solve Problems?
5. http://microservices-buch.de/ http://microservices-book.com/
6. Microservices?
7. UNIX Philosophy > Write programs that do one thing and do it well > Write programs to work together > Write programs with a common interface
8. Definition Microservice > Independent deployment unit > Separate data handling & storage > Should include UI > Order process, Billing, Catalog… > Process > VM > Docker container Server Micro Service
9. Deployment Monolith > Might be 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 Deploy Deploy Deploy Deploy Automated Reproducible Fast
11. Continuous Delivery: Build Pipeline Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing Release Deploy Deploy Deploy Deploy Billing
12. Continuous Delivery Pipeline too complex or slow?
13. Continuous Delivery Pipeline too complex or slow? Consider changing the architecture!
14. Microservices: Challenges > 50 or 100 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 Complete System Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing
16. Integration Tests Tests Microservices Unit Tests
17. Microservices can only be deployed independently if tests are independent!
18. Microservices can only be deployed independently if your Continuous Delivery Pipeline works.
19. Microservices + Continuous Delivery!
20. Why all the hassle?
21. Conway‘s Law Architecture copies communication structures of the organization
22. Conway’s Law as a Limit > Organization drives architecture > Teams of experts > i.e. UI, logic & database team > Three technical artifacts
23. E Commerce Shop Change Order Process! UI Logic DB
24. time DB Team Sprint Logic Team Sprint GUI Team Sprint 3 sprints
25. Order Search Billing Team for each business feature Let architecture drive the organization Order Billing Search
26. Deployment Monolith + Conway’s Law Deployment Monolith Stories Technical Coordination Coordinating Releases Stories Stories Order Billing Search
27. Team can deploy without 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 Search Billing Order Billing Search
28. Microservices Microservice Stories Technical Coordination Microservice Stories Technical Coordination Microservice Stories Technical Coordination Order Billing Search Release Release Release
29. Microservices: Challenges > Deployment? > Monitoring? > Log Analysis? Ops
30. Micro- and Macro- Architecture
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- Architecture for Ops > Macro > Define Log Analysis, Monitoring, Deployment tools > Defined globally > Micro > Concrete deployment, monitoring, logging > Defined per team / Microservice
34. Microservices Teams need many technical skills.
35. Microservices Teams need Ops.
36. DevOps
37. DevOps / Microservices > Teams consist primarily of Devs > Devs interested in Docker, ELK ... > ... lots of experience in Ops > More Ops effort
38. Microservices = huge opportunity for Ops!
39. How Much DevOps is 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 Dev Ops Common Technologies Log, Monitoring, Deployment
41. DevOps = Collaboration not Organization
42. This changes software development fundamentally.
43. Maintainability
44. Maintainability: Classical Approach > Clear architecture > Good code quality > Many tests Dev
45. Maintainability: New Approach Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing Release Fast und Reliable Fast Feedback
46. Maintainibility: New Approach > Continuous Delivery simplifies roll out > ...and test them > ...and monitor them > Microservices limit size and risk of changes DevOps
47. Scalability
48. Scalabilty: Classical Approach > Implement technical constraints > E.g. statelessness > Use appropiate technologies Dev
49. Performance Risk > Hard to really predict performance > Load test simulate user on a different environment
50. Scalability: Alternative Approach > Don‘t do anything stupid in the architecture > Identify bottleneck > Eliminate bottleneck > Common technique
51. Enable Alternative Approach > Monitoring to identify bottleneck > Fast deployment to eliminate bottleneck DevOps
52. Maintainability: New Approach Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing Release Fast Monitor all relevant data
53. Conclusion
54. Conclusion > Synergy: Microservices and Continuous Delivery > Microservices and Continuous Delivery support and require DevOps > DevOps = Collaboration > Enable alternative approaches e.g. to maintainability and scalability
55. Thank You! @ewolff