Software Architecture


Fundamentals of Software Architecture: An Engineering Approach
Clean Architecture
Designing Data-Intensive Applications
Building Microservices: Designing Fine-Grained Systems
Domain-Driven Design: Tackling Complexity in the Heart of Software
Software Architecture: The Hard Parts: Modern Trade-Off Analyses for Distributed Architectures
Building Evolutionary Architectures: Support Constant Change
Software Architecture in Practice
Patterns of Enterprise Application Architecture
The Software Architect Elevator: Redefining the Architect's Role in the Digital Enterprise
Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith
Learning Domain-Driven Design: Aligning Software Architecture and Business Strategy
Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions (Addison-Wesley Signature Series (Fowler))
Just Enough Software Architecture: A Risk-Driven Approach
Design Patterns: Elements of Reusable Object-Oriented Software
Fundamentals of Software Architecture by Mark   RichardsClean Architecture by Robert C. MartinDesigning Data-Intensive Applications by Martin KleppmannMonolith to Microservices by Sam NewmanDocumenting Software Architectures by Paul Clements
Software architecture
23 books — 6 voters

Software Architecture in Practice by Bass Len
Software Architecture Books
1 book — 1 voter
Clean Architecture by Robert C. Martin12 More Essential Skills for Software Architects by Dave HendricksenSoftware Systems Architecture by Nick RozanskiSoftware Architecture by Mary    ShawDesign Patterns by Erich Gamma
Mastering Software Architecture
44 books — 6 voters


Neal Ford
All too often architects make a decision that is the correct decision at the time but becomes a bad decision over time because of changing conditions like dynamic equilibrium. For example, architects design a system as a desktop application, yet the industry herds them toward a web application as users’ habits change. The original decision wasn’t incorrect, but the ecosystem shifted in unexpected ways.
Neal Ford, Building Evolutionary Architectures: Support Constant Change

[...] you shouldn't be uneasy about any parts of the architecture. It shouldn't contain anything just to please the boss. It shouldn't contain anything that's hard for you to understand. You're the one who'll implement it; if it doesn't make sense to you, how can you implement it? ...more
Steve McConnell, Code Complete: A Practical Handbook of Software Construction

More quotes...
Group for book recommendations by Thoughtworkers
17 members, last active 2 years ago
My Tech Reads Bits of knowledge from the most influential IT reads.
4 members, last active 8 years ago
The Clean Architecture Ukraine Group of software engineers from Ukraine who use The Clean Architecture.
1 member, last active 3 years ago
apploft. Book Club apploft. GmbH
8 members, last active 4 years ago