Software architecture in a DevOps world
0 likes385 views
The document discusses how software architects can work with DevOps teams by applying DevOps principles to software architecture. It defines DevOps as development and operations engineers working together across the entire product lifecycle. Key DevOps principles that can be applied to architecture include focusing on customer needs, enabling automation, ensuring collaboration between teams, prioritizing continuous improvement through experimentation and feedback, and taking an approach of gradual changes. The document argues that by following these principles, architects can help their organizations build and release better quality software more quickly.
Ad
More Related Content
What's hot (20)
Similar to Software architecture in a DevOps world (20)
Ad
Recently uploaded (20)
![Download Wondershare Filmora Crack [2025] With Latest](https://cdn.slidesharecdn.com/ss_thumbnails/neo4j-howkgsareshapingthefutureofgenerativeaiatawssummitlondonapril2024-240426125209-2d9db05d-250419-250428115407-a04afffa-thumbnail.jpg?width=560&fit=bounds)
Ad
Software architecture in a DevOps world
- 1. [email protected] Software architecture in a DevOps world Bert Jan Schrijver @bjschrijver
- 2. Bert Jan Schrijver L e t ’ s m e e t @bjschrijver
- 3. Why DevOps? Principles of DevOps What is DevOps? Introduction Flexibility in software Conclusion Q&A Outline Software architecture in a DevOps world DevOps applied to software architecture @bjschrijver
- 4. • Sum of all decisions taken during development • Making design decisions about important stuff • Enabling a team to build software that provides solutions for business problems What is software architecture?
- 5. Definitions Every change goes through the build/test pipeline and automatically gets put into production. Continuous Deployment ?! DevOps Building and testing software in such a way that the software can be released to production at any time. "Ship early, ship often, sacrificing features, never quality" - Kyle Neath Continuous Delivery Team members integrate their work frequently. Commits are verified by automated builds and tests. Continuous Integration Who’s who in CD & DevOps @bjschrijver
- 6. DevOps: a definition Development and operations engineers being responsible together for the entire lifecycle of a product.
- 7. : building and running better-quality software more quickly and more reliably. Developers and other IT professionals working together on a shared goal DevOps: another definition
- 8. DevOps: another definition ;-) A set of practices intended to reduce the time between committing a change to a system and the change being placed into normal production, while ensuring high quality.
- 9. Why DevOps? as an enabler for Continuous Delivery, faster problem resolution and focus on value instead of problems. DevOps makes your business move faster
- 10. What is DevOps really about?
- 11. DevOps is about culture Source: http://www.azmc.org/wp-content/uploads/2012/11/Arts-and-Culture-Large.jpg
- 12. DevOps is about freedom and responsibility Source: https://images.unsplash.com/photo-1449177009399-be6867ef0505
- 13. DevOps is about empathy Source: http://www.scarymommy.com/wp-content/uploads/2014/06/empathy.jpg
- 14. Principles of DevOps @bjschrijver Continuous improvement Automation Ownership Experimentation Gradual changes Customer oriented Collaboration
- 15. Software architecture and DevOps
- 16. • Applied to software architecture: • Start with the simplest solution you can come up with • Improve and refine along the way • Focus on dealing with uncertainty • Do just enough architecture to get through the next sprint ;-) DevOps principle: gradual changes
- 17. • Applied to software architecture: • Focus on the business’ needs • Don’t design for yourself! • Help out with clarifying non-functional requirements DevOps principle: customer oriented
- 18. • Applied to software architecture: • Diagram generation • Automated architecture checks • Infrastructure as code -> cloud architecture DevOps principle: automation
- 19. • Applied to software architecture: • Team owns the architecture • Architect needs to be involved with the team • Architect is accountable for the end result too! • Minimise dependencies to things outside the team DevOps principle: ownership
- 20. DevOps principle: ownership Source: https://architectelevator.com/architecture/organizing-architecture
- 21. • Applied to software architecture: • Talk to all stakeholders • Developers are stakeholders as well! • Be transparent, explain decisions, be open for feedback • No room for ivory towers DevOps principle: collaboration
- 22. • Applied to software architecture: • Do proof of concepts to gain insights • Try to solve problems early • Embrace failure • Don’t be afraid to start over (.. an iteration worth of work) DevOps principle: experimentation
- 23. DevOps principle: experimentation Source: https://www.linkedin.com/posts/gergelyorosz_architecture-softwaredesign-bigtech-activity-6851431869691523072-2wbf/
- 24. • Applied to software architecture: • Focus on feedback loops • Ask developers for feedback! • Measure & monitor • Evolving architecture instead of up-front • Software architecture is never finished DevOps principle: continuous improvement
- 25. Continuous Delivery & DevOps sound great, but it won’t work here… “ ” Photo: Dave Lehl, text source: Jez Humble
- 26. “CD & DevOps won’t work here” • Stated reasons: • we’re regulated • we’re not building websites • too much legacy • our people are too stupid • Actual reasons: • our culture stinks • our architecture stinks Photo: Dave Lehl, text source: Jez Humble Source: talk by Jez Humble https://www.youtube.com/watch?v=837Z_oehhRg
- 27. About flexibility in software…
- 28. Summary
- 29. How do you work as an architect with(in) a DevOps team?
- 30. By applying the same DevOps principles to the domain of software architecture.
- 34. Thanks for your time. Got feedback? Tweet it! All pictures belong to their respective authors @bjschrijver