The document discusses how software architects can work with DevOps teams by applying DevOps principles to software architecture. Some key points made are: 1) DevOps principles like gradual changes, customer orientation, automation, ownership, collaboration, experimentation and continuous improvement can be applied to software architecture practices. 2) Architects should focus on the business needs, involve developers as stakeholders, evolve architectures through feedback rather than upfront design, and embrace failure through experiments. 3) Flexible architectures that can change based on needs are preferable to rigid pre-defined architectures in a DevOps context.

1. bertjan@openvalue.eu
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
• Allows you to build systems that are beyond
the scale that you can hold in your head
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
• Identify high level components
• Improve, refine and evolve 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
• Architecture is about tradeoffs
DevOps principle: customer oriented

18. • Applied to software architecture:
• Diagram generation
• Automated architecture checks
• Infrastructure as code, automated
provisioning of cloud architecture,
autoscaling
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. “Highly specific code is often preferable
to sophisticated configuration”
Stefan Tilkov

29. Summary

30. How do you work as an architect
with(in) a DevOps team?

31. By applying the same DevOps principles
to the domain of software architecture.

32. Source: https://cdn2.vox-cdn.com/thumbor/J9OqPYS7FgI9fjGhnF7AFh8foVY=/148x0:1768x1080/1280x854/cdn0.vox-cdn.com/uploads/chorus_image/image/46147742/cute-success-kid-1920x1080.0.0.jpg
THAT’S IT.
NOW GO KICK SOME ASS!

33. Source: https://cdn2.vox-cdn.com/thumbor/J9OqPYS7FgI9fjGhnF7AFh8foVY=/148x0:1768x1080/1280x854/cdn0.vox-cdn.com/uploads/chorus_image/image/46147742/cute-success-kid-1920x1080.0.0.jpg
THAT’S IT.
NOW GO KICK SOME ASS!

34. Questions?
@bjschrijver

35. Thanks for your time.
Got feedback? Tweet it!
All pictures belong
to their respective
authors
@bjschrijver