Architectures and Alternatives

Limiting software architecture to the traditional ideas is not enough for today's challenges. This presentation shows additional tools and how problems like maintainability, reliability and usability can be solved.

Transcript

1. http://continuous-delivery-buch.de/ http://continuous-delivery-book.com/
2. http://microservices-buch.de/ http://microservices-book.com/
3. http://microservices-book.com/ primer.html http://microservices-buch.de/ ueberblick.html FREE!!!!
5. What is Architecture? What is an Architect?
6. Software Architecture > Definition ISO 42010 Fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution
7. Architecture = Boxes & Arrows
8. Software Architect? > A title? > A role! > …in particular in agile teams. > Anyone / someone is doing architecture
9. Software Architect? > Designer > …like an architect for buildings
10. Architecture= Boxes + Arrows Architect= Designer Role
11. Conway’s Law Architecture copies communication structures of the organization
12. Current Frontend Backend
13. Goal
14. Current Frontend Backend
15. Current Frontend Backend
16. Goal
17. Reorganization!
18. Reorganization!
19. Current: New goal?
20. Current: New goal?
21. New Goal
22. Architecture > If architecture = organization > …then change to architecture = reorganization > …or organization is a constraint.
23. Goal
24. Goal: Self-contained System http://scs-architecture-org
25. Result
26. Result
27. Architecture > Developers’ skills and preferences drive technology decisions. > Technology decisions can drive architecture.
28. Architecture= Boxes + Arrows +Org Architect= ?
29. Why do we even care about Architecture?
30. Maintainability!!
31. Quality Attributes > ISO 25010 > E.g. reliability > Usability > Maintainability > ...and a lot more
32. Architecture= Quality Attributes Architect= ?
33. Quality Attributes > Reliability > Usability > Maintainability
34. Reliability > Software has to be available > Clean architecture & code – any impact?
35. Reliability > Software has to be available > Classic approach: > Highly available hardware > Run in a cluster > …and cluster-enabled software
36. Reliability
37. Reliability > ISO 25010: Availability / Fault tolerance > ISO 25010: Recoverability
38. Reliability > Highly available hardware > …and cluster > …focus on MTBF (Mean time between failure)
39. Decrease MTTR - How?
41. Decrease MTTR – How? > Find a problem faster > Measure > Monitoring > Logs > Alerts…
42. Decrease MTTR – How? > Get the fix out faster > Deployment > …or fail-over
43. Decrease MTTR – How? > Monitoring and Deployment: > Ops challenges > …not classic architecture
44. Architecture= Quality Attributes+Org Architect= ?
45. Quality Attributes > Reliability > Usability > Maintainability
46. Usability > ISO 25010 > Learnability > Ease-of-use > Attractiveness
47. Usability > Might be very important > …e.g. to gain a huge market share. > How do you make it happen?
48. Architecture = Boxes & Arrows
49. Usability??
50. Some Ideas to Improve Usability > Hire an UX expert > Usability tests > Prototypes + feedback > Look at support cases / hotline calls
51. Some Ideas to Improve Usability > No traditional architecture > QA / Organization / Project management
52. Usability > Quality attribute > Part of the technical decisions > Beyond “usual” architecture measures
53. Architecture= Quality Attributes+Org Architect= ?
54. Quality Attributes > Reliability > Usability > Maintainability
55. Maintainability > Clean architecture! > I am waiting for such a customer.
56. We can achieve maintainability with clean architecture + clean code.
57. Clean Architecture
58. Developer
59. Developer
60. Result?
62. ECommerce System Order Catalog Billing Search Module = microservices
63. ECommerce System Order Catalog Billing Search Module = microservices Communication e.g. REST
64. REST REST
65. ECommerce System Order Catalog Billing Search Dependencies between systems cannot sneak in
66. ECommerce System Order Catalog Billing Search Dependencies between systems cannot sneak in
67. ECommerce System Order Catalog Billing Search Dependencies between systems cannot sneak in “Architecture Firewalls”
68. “Architecture Firewall” like REST enforce the architecture
69. ECommerce System Order Catalog Billing Search Microservices small
70. ECommerce System Order Catalog Billing Search Microservices small Hard to mess up
71. ECommerce System Order Catalog Billing Search Microservices small Hard to mess up
72. ECommerce System Catalog Billing Search Microservices small Hard to mess up
73. ECommerce System Order Catalog Billing Search Microservices small Hard to mess up Replace if messed up.
74. Small, independent deployable microservices are recyclable.
75. Recycle your software! !
76. How many people are trying to replace legacy systems?
77. Replaceability is usually no goal for a software project. Why??
78. We can achieve maintainability with clean architecture + clean code
79. We can achieve maintainability with architecture firewalls + recyclable microservices
80. Maintainability > Clean architecture focuses on Changeability. > …and Analyzability. > There is more!
81. Testability > Another contributing to maintainability > IMHO: Should be tests, not just testability > Bonus if tests need not be changed for refactoring. > Unit tests? > Acceptance tests?
82. Deployment > It’s nice to change code. > It’s (lean) waste until it is in production. > Deployment: another factor for maintainability.
83. Commit Stage Automated Acceptance Testing Automated Capacity Testing Manual Explorative Testing Release QA Dev Ops
84. Maintainability > Not clean architecture and code > Recyclable, very decoupled microservices > Not just structure of the system, but also > …test and deployment > …continuous delivery pipeline
85. Maintainability > Not just architect and Dev, but also > QA and Ops
86. Architecture= Quality Attributes+Org Architect= ?
87. Achieving the Attributes > Organizational Measure (e.g. hire UX) > Cross-functional: Ops, Dev, QA
88. Architect? > Technical manager > In charge of achieving the quality attributes > Influencing organization > …and Ops, Dev, QA
89. Agile Team > Self Organization > i.e. not necessarily a defined architect > Architecture activities cover Ops, Dev, QA > Cross-functional!
90. Architecture= Quality Attributes+Org Architect= Technical Management Role