Continuous Delivery, DevOps, Cloud - New Requirements for New Architectures

How Continuous Delivery, DevOps and Cloud influence Software Architecture - and how it all helps to achieve the goals for the system.

Transcript

1. Continuous Delivery, DevOps, Cloud - New Requirements for New Architectures Eberhard Wolff Fellow, innoQ @ewolff
3. http://microservices-buch.de/ http://microservices-book.com/
4. Architecture? Modularization Quality Attributes
5. Scenario “Support Different Mobile platform” Scenario “Search faster than 5s” Efficency Latency Cost Security Data privacy Secrecy Integrity Maintainability Understandability Changeability Portability Changeability Availability User error Hardware failure Recovery time Usability Time to learn
6. Know the needed quality attributes! Find technical solutions for them!
7. ECommerce Order Customer Delivery Ca. 100 developers QA Operations Software modules How to test? Manual Hand over Manual Hand over How to operate? Scalability Availability Changeability Architecture
8. Continuous Delivery (CD)
9. Continuous Delivery (CD) Pipeline >  Better Time-to-Market >  Reproducible tests and deployments >  More tests >  Deployment = natural part of the process Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing Release
10. Software more reliable and easier to change.
11. ECommerce Order Customer Delivery Ca. 100 developers QA Operations Software modules How to test? Manual Hand over Manual Hand over How to operate? Architecture Scalability Availability Changeability Continuous Delivery
12. That will never work with my (legacy) system! Was it built with CD in mind?
13. Quality Attributes for Continuous Delivery >  Simple Deployment >  …simplifies automation >  Easy testing >  …for acceptance tests, too >  ...probably API, not UI-based >  Hexagonal Architecture: Tests = another client
14. Quality Attributes for Continuous Delivery >  Make deployment less risky >  Resilience >  i.e. failure of one module should not make other modules fail >  Bulkhead
15. Continuous Delivery >  Supports Quality Attributes >  Changeability >  Demand Quality Attributes >  Simple Deployment >  Good testability >  Resilience
16. Size Matters! >  Large applications hard to deploy >  Hard to test >  Lots of regression testing >  Hard to roll back / safeguard deployments
17. Small and independent deployment units Microservices
18. Microservices solve all problems? >  Probably not >  But: Software Architecture was about modules and development >  It should be about testing, deployment and operations, too!
19. ECommerce Order Customer Delivery Ca. 100 developers QA Operations Software modules How to test? Manual Hand over Manual Hand over How to operate? Scalability Availability Changeability
20. ECommerce Order Customer Delivery Ca. 100 developers QA Operations Software modules How to test? How to operate? Architecture Scalability Availability Changeability Continuous Delivery
21. Need different skill set
22. DevOps=
23. DevOps= Development + Operations collaborate
24. ECommerce Order Customer Delivery Ca. 100 developers QA Operations JVM ClassLoader App Server No visibility in production App-specific metrics Kernel I/Os CPU Monitoring, alarms
25. DevOps Architecture >  Broadens scope of architecture >  What are relevant metrics? App or OS >  How to monitor? >  Alarm if? >  Provide access to full team
26. Cloud
27. Cloud… >  …is an inexpensive environment for applications >  …in particular for elastic scaling
28. Efficency Latency Cost Security Data privacy Secrecy Integrity Maintainability Understandability Changeability Portabiity Changeability Availability User error Hardware failure Recovery time Usability Time to learn
29. Cloud… >  …is an inexpensive environment for applications >  …in particular for elastic scaline
30. Why Did Amazon Build a Cloud?
31. Significant investment
32. No enterprise grade free virtualization
33. Cost?
34. Optimize resource utilization?
35. Lots of server used only for the holiday season.
36. Lots of server used only for the holiday season.
37. Developers spent more time on scaling than on features.
38. Cloud = universal scalable infrastructure
39. ECommerce Order Customer Delivery Ca. 100 developers QA Operations Software modules How to test? How to operate? Architecture Scalability Availability Changeability Continuous Delivery
40. Scaling >  Traditional: Architecture will solve it >  Cloud: Start more server >  …if load increases >  Pay-as-you-go
41. Scaling >  Traditional: Architecture enables scaling >  There will be bottlenecks >  But: Hard to know bottleneck >  Monitoring to identify bottleneck >  Continuous Delivery to deploy fixes for bottleneck
42. ECommerce Order Customer Delivery Ca. 100 developers QA Operations Software modules How to test? How to operate? Architecture Scalability Availability Changeability Continuous Delivery
43. There is more to Cloud…
45. Oracle instance = One click
46. Why should a Software Engineer care??
47. Cloud = Components
48. Instagram >  Global photo sharing >  S3 storage >  Cloudfront Content Delivery Network >  Custom code >  3 engineers (Dev and Ops) >  10 mio user >  100 mio photos
49. Efficency Latency Cost Security Data privacy Secrecy Integrity Maintainability Understandability Changeability Portabiity Changeability Availability User error Hardware failure Recovery time Usability Time to learn
50. Enabler Continuous Delivery / DevOps >  Much easier deployment >  Create server, deploy software – via API >  Integrated Monitoring
51. All for free???
52. Amazon SLAs on One Slide >  If one of our data centers fails… >  Well, that’s your problem >  And we do reboot your server randomly.
53. #SRSLY?
54. Amazon SLAs on One Slide >  If a data center fails >  Well, that’s your problem >  And we do reboot your server randomly. >  But you can always start new servers >  …in other data centers >  ...or regions
55. Global redundancy across data centers
56. Efficency Latency Cost Security Data privacy Secrecy Integrity Maintainability Understandability Changeability Portabiity Changeability Availability User error Hardware failure Recovery time Usability Time to learn
57. Dynamic Scaling & Availability >  Start more server >  …if servers crash >  Architecture must be stateless >  Servers must handle load from the beginning
58. Resilience >  Systems might reboot or crash >  …so client fail >  Deal with failure
59. The Cloud Paradox >  Unreliable hardware >  …and not too powerful hardware >  …are the ideal foundation for reliable & scalable software.
60. Deal with failure – don’t try to fight it.
61. Cloud >  Supports Quality Attributes >  Scaling >  Time-to-Market >  Availability >  Demand Quality Attributes >  Resilience
62. Conclusion
63. Conclusion >  Know the desired quality attributes!
64. Know the desired quality attributes!
65. Conclusion >  Know the desired quality attributes! >  Continuous Delivery >  Demands smaller, easier to deploy units >  Demands testability >  Offers changeability
66. Conclusion >  DevOps enables CD architectures >  …brings other experts to the teams >  Scalability = Monitoring + fast deployment?
67. Conclusion >  Cloud: Scaling >  …and fast time-to-market >  ...and availability