DevOps and Microarchitectures - Why Technology Choices Matters

Transcript

1. Devops And Microservices architecture Agile tech stacks Marcus Ahnve @mahnve m@hnve.org
2. About Me • Playing agile coach Programmer • Professional developer since 1996 • Polyglot a.k.a web developer • Founder of Agila Sverige
3. tldr; Agile methodologies require supporting technology to reach their full potential
4. What Is ... Easy to implement Applicable to all kinds of projects Fully scalable ?
5. The Promise of Agile “The reason that Scrum has become the leading agile method is among other things that it is so easy to implement, it can be applied to every kind of project and is fully scalable”
6. What we forgot
7. Three Levels of Agility Technology Scrum Management
8. Todays Focus Technology Scrum Management
9. Cobol
10. Traditional Architectures Reuse Resource Availability Stakeholder Focus
11. Platforms
12. Cobol
13. Java
14. Vendor Platforms
15. Lost XP Practices TDD Simple Design Refactoring Continuous Integration Small Releases
16. Platforms Are Oneway Deadend Streets
17. Lost XP Practices TDD Simple Design Refactoring Continuous Integration Small Releases
18. Lost Lean Ambitions Defer Decisions
19. Software lifecycle Does not include Death Who pays for a system that is hard to replace?
20. We Create Systems that Are Hard To Replace
21. Ask “How will we replace it?” Smaller parts Implementation not that important Communication however is
22. Split into smaller part Login Admin Public Follow the Stories and Actors
23. Example A B C D
24. What Data To Send? A B C D ? ? ?
25. SOAP A B C D B B A
26. Self describing services A B What do you want? X, Y and Z Here you go
27. XHTML A B GET XHTML FORM POST
28. Hypermedia Client Service <service> <...> <link rel=”” href=”...” /> </service>
29. Fault tolerance Login Admin Public Public Public
30. Releasability Login Admin Public
31. Scalability Login Admin Public Public Public
32. Splittability Login Admin Public Login Admin Public
33. Simple vs. EASY Function ality
34. Simple vs. EASY Productiv ity
35. The next problem
36. Manual Deploys
37. It can get worse It can get worse
38. The Tail Is Wagging the Dog
39. The Cost Of Late Releases
40. Developers who like operations Operations who like development DevOps
41. Server provisioning should be repeatable
42. Tooling
43. Who is responsible? Hardware OS Infrastructure Application Logic
44. Different Slicing Hardware OS Infrastructure Application Logic Infrastructure
45. How to do it
46. Deploys should not be scary
47. How often can you deploy? Weekly? Daily? Hourly?
48. Deploys should not be scary
49. How to change organizations
50. Use Real States What used to be “Done” is now inventory
51. Agile should have been Adaptive
52. Thank you! Marcus Ahnve @mahnve m@hnve.org