Is Software Architecture Really Necessary?

Software architecture often feels like an unnecessary burden—introducing complexity and slowing down the process of just writing code. Why not skip it altogether? This talk explores whether it’s possible to develop software without architecture and examines the implications of doing so. We’ll uncover why architecture inevitably emerges, whether explicitly designed or not. We’ll discuss the relationship between architecture and qualities like performance, maintainability, and usability, and how these qualities shape the success of any project. Finally, we’ll reflect on the balance needed in architecture—avoiding both overengineering and the pitfalls of "architecture theater"—to focus on solving real-world problems effectively. Whether you are a seasoned architect or a skeptical developer, this session will challenge your perspective on what software architecture truly means and how much of it your project really needs.

Transcript

1. Is Software Architecture Really Necessary? Eberhard Wolff Head of Architecture https://swaglab.rocks/ https://ewolff.com/
2. Yes? You do software architecture? Wow! Probably you do it, too…
3. An Example
4. Example •Sitting at the computer •Writing some code •Reimplementing an importer for some data •Just one person •Looks simple •This is basic software development. •Surely, I am not doing architecture?
5. What is Architecture?
6. https://software-architektur.tv/2022/02/11/folge109.html
7. What is Software Architecture? “Architecture is about the important stuff. Whatever that is.” Ralph Jonson https://martinfowler.com/architecture/
8. Architecture = Important Stuff •There is always something important. •So, there is always architecture. •But what is important? •Is this definition helpful? •Almost chauvinistic: Architecture is important. The rest isn’t.
9. Architecture: Alternative Definition Architecture Structure Technology decision Quality requirement a.k.a. non-functional requirements e.g. performance, maintainability, security, user friendliness, …
10. Back to the Example •Why is the importer rewritten? •Lack of maintainability? •Lack of performance? •Other reasons?
11. Architecture: Alternative Definition Architecture Structure Technology decision Quality requirement Quality requirement not reached Revise to reach quality attributes Revise to reach quality attributes
12. Rewriting the Importer •Quality requirements not matched •Architecture decision: rewrite Ruled-out options: e.g. improve just a part of the code •Must decide about technologies •Must decide about structure •Should reach quality requirement after rewrite
13. Rewriting the importer is an architecture exercise!
14. What Does That Mean for Architecture? •Developer does architecture in this case. •There is not really anything magic about it. •There are some pretty weird ideas about what architecture is.
15. Probably you do architecture, too…
16. Is software architecture really necessary?
17. Can we opt out of software architecture?
18. Architecture: Alternative Definition Architecture Structure Technology decision Quality requirement
19. Can We Opt Out of Software Architecture? •There will be quality requirements. •There will be a structure of the system. •There will technology decisions. •You can’t opt out of software architecture.
20. Can We Opt Out of Software Architecture? •You can just ignore software architecture …i.e. make random decisions …without thinking too deeply about it …which is probably not “opt out”. •And the results will probably be unpleasant…
21. What Now? •Opt in to software architecture! •Lots of decisions •Make them explicit!
22. Decisions •Lots of decisions! •Even more options! •Each decision is the death of all options but one.
23. First Decision •First decision: Priorities •E.g. whatever caused the rewrite – you better fix it! •E.g. performance •So make sure performance is met. •Understand why the current solution is too slow •Load tests?
24. More Priorities •When is the last responsible moment? •Later means more information and better decisions. •Subjective – and depends on courage
25. Decisions •Might be intuitive •Might need to be documented •Might need to be revised
26. Architecture Decision Record (ADRs) Status Context Decision Consequences Michael Nygard We have several clients who are stabilizing their current systems, … but looking toward a larger rearchitecture in the not-too- distant future. By writing these intentions down, we don't inadvertently make those future changes harder.
27. Architecture •Architecture is a means to an end (a successful project) •As little architecture work as possible •But how little is enough? •For an importer one persons writes, no document might be needed.
28. Team
29. Team •More developers …or your future self •Documentation becomes more important. •Process becomes more important.
30. Traditional Architect •Most Experienced Person •For every detail? •For every technology? •Unrealistic •Making all important decisions •Puts enormous pressure on the architect. Architects
31. Most Experienced Person •Quite sad •Use the technical expertise of the team •...and grow the team Architects Team
32. Understanding the System •Architects need to understand the system. •Systems too large for one person. •Use expertise of the team! •Each one will understand some part. Architects Team
33. Traditional Architect •Define the architecture •i.e. make all relevant decisions •Enforce the architecture Architects
34. Decisions •Understand the team’s problems •Seek feedback about possible decision •Communicate decisions Architects Team
35. Quality of Decision vs Autonomy •Decisions have two levels: •Quality of the decision •How the decision is made impacts autonomy •E.g. let the team decide or push a decision through
36. Quality of Decision vs Autonomy JavaScript Framework: Architect pushes decision through Quality of the Architecture Autonomy Architect probably thinks the decision is great Team might actually have some expertise.
37. Quality of Decision vs Autonomy Quality of the Decision Autonomy Team might actually have some expertise. Even if it is great – is it worth it? Architect probably thinks the decision is great JavaScript Framework: Architect pushes decision through
38. Quality of Decision vs Autonomy JavaScript Framework: Let the team decide Quality of the Decision Autonomy
39. Decisions •Moderate, listen, convince •Don’t enforce •Make your expertise usable •General rule for managing self-organization Architects Team
40. Why seems an opt-out of software architecture possible?
41. Why Opt-out Seems Possible •Architecture always exists. •But it might not be explicit. •No documentation •Not too complex
42. Why Opt-out Seems Great •Architecture and architect might be disconnected from reality. •Ivory tower •Result: Resistance
43. Why Opt-out Seems Great •Architecture might be bureaucracy •Unnecessary documentation
44. Can you have too much architecture?
45. Too Much Architecture? •Too much effort for too little result •i.e. too much documentation for too little code •How much documentation would you write for the importer?
46. Too Little Architecture? •Not thinking about quality goals •Not deciding about a great structure
47. What is typical? Too little or too much architecture?
48. Too Little vs. Too Much •Too little: You end up with an architecture mess. •Too much: Bureaucracy
49. Do We Do Too Little or Too Much? •Crossovers: Software engineers who used to be engineers in other fields •Crossovers seem to think we should use a more methodical process. https://hillelwayne.com/post/what-we-can-learn/
50. https://software-architektur.tv/2024/03/27/folge209.html
51. Architecture Theatre •Kevlin Henney •Can there be too much architecture? •Hierarchical, bureaucratic, committee-driven approach opposes to the very idea of actually developing software example of 'not enough architecture’ 'pure architecture theatre' https://mastodon.social/@kevlin/112003129757159797
52. Architecture and AI •LLM generate an architecture documentation = “architecture theatre”? •Lots of text …but no thought process …and probably no real decisions …or open questions
53. https://software-architektur.tv/2024/01/26/folge199.html
54. https://software-architektur.tv/2025/04/11/episode260.html
55. Conclusion
56. Is Software Architecture Really Necessary? •Software architecture = structure + technical decisions •Driver: Quality requirements •You can‘t opt-out of software architecture! •But you can give it too little thought …or play architecture theatre.
57. DRINK A VIRTUAL COFFEE WITH ME! https://calendly.com/eberhard-wolff-swaglab/
58. Download here! Send email to jax2025@ewolff.com Slides + more Powered by Amazon Lambda & Microservices Email address logged for 14 days, wrong addressed emails handled manually