
Although salary surveys worldwide regularly identify software architect as one of the top ten best jobs, no decent guides exist to help developers become architects. Until now. This practical guide provides the first comprehensive overview of software architecture's many aspects. You'll examine architectural characteristics, architectural patterns, component determination, diagramming and presenting architecture, evolutionary architecture, and many other topics. Authors Neal Ford and Mark Richards help you learn through examples in a variety of popular programming languages, such as Java, C#, JavaScript, and others. You'll focus on architecture principles with examples that apply across all technology stacks.
Tech book recommendations: 'Secure by Design', 'Designing Data-Intensive Applications', 'Building Secure and Reliable Systems' and 'Fundamentals of Software Architecture'.
For scifi: 'Murderbot Diaries' and 'The Expanse' - both are just great entertainment
- Just Enough Software Architecture
- Domain Driven Design - Tackling Complexity in the Heart of Software (Eric Evans) I recommend this one more than Vaughn Vernon's DDD.
- Clean Architecture (Robert Martin)
- Fundamentals of Software Architecture: an Engineering Approach
- Design Patterns (Gamma et al)
- Site Reliability Engineering: How Google Runs Production Systems
- Refactoring: Improving the Design of Existing Code (2nd Edition) (Addison-Wesley Signature Series (Fowler))
- Refactoring to Patterns
- Patterns of Enterprise Application Architecture
-Head First Design Patterns Building Extensible and Maintainable Object Oriented Software and I
- https://www.youtube.com/watch?v=odxOPxYJdjg
- "Architecture Modernization: Socio-technical alignment of software, strategy, and structure"
- Software Architecture in Practice
- Documenting Software Architectures: Views and Beyond
- Head first: Software Architecture
2 chapters weekly worked well because the chapters were short, and were mostly brief overviews that discussed the pros and cons. (Also we had a ton of experience in the room, so that helped guide the discussion.)
If the chapters were dense I would have longer gaps between meetings to allow people more time to read and reflect.
- Building Event-Driven Microservices
- Building Evolutionary Architectures
- Building Micro-Frontends
- Continuous API Management
- Flow Architectures
- Foundations of Scalable Systems
- Fundamentals of Software Architecture
- Learning Domain-Driven Design
- Mastering API Architecture
- Microservices Up and Running
- Monolith to Microservices
- Software Architecture Metrics
- Software Architecture: The Hard Parts
- The Art of Agile Development
- The Software Architect Elevator