To have context for the other references, I find the following resources essential:
- Who needs an Architect? (Martin Fowler)
- Competing On The Basis Of Speed (Mary Poppendieck) Optimizing for speed, flow, and waste reduction. Lean Software Development
As general resources:
- Agile Architecture Keynote Molly Dishman & Martin Fowler
- Evolutionary Architecture & Micro-Services Rebecca Parsons
- Evolutionary Software Architectures Neal Ford
- Clean Architecture Robert C. Martin
- Embracing Uncertainty Dan North
- The art of destroying software Greg Young
- Lean Software Development
- Lean Principle #4 – Defer Commitment
- https://martinfowler.com/bliki/SacrificialArchitecture.html
- https://martinfowler.com/bliki/Yagni.html
- https://martinfowler.com/bliki/ParallelChange.html
- https://martinfowler.com/bliki/BranchByAbstraction.html
- https://martinfowler.com/bliki/FeatureToggle.html
- https://martinfowler.com/books/refactoringDatabases.html
- https://martinfowler.com/articles/evodb.html
To document all the decisions you make to gain the sharing understanding of the design:
We also need a lot of tricks for our bag of tricks to have different approaches for different problems... Related with this, I think is important to have knowledge about:
- DDD mainly the strategic patterns and the bounded context concept
- Microservices (once you are a master of the monolith of course)
- CQRS
- Continuous delivery (and all the things that require)
- Reactive systems
- Enterprise integration patterns and Patterns of Enterprise Application Architecture
- ...
No comments:
Post a Comment