#Architecture Strategy
10 articles
Differentiating Architecture Strategy, Tactics, and Design
Differentiate architecture strategy, tactics, and design using 5W1H framework to clarify why, what, how, when, where, and who decisions.
Good Architecture Strategy, Bad Architecture Strategy
Even when you write an architecture strategy, it sometimes fails to work, ending up as a strategy in name only or never being executed. Drawing on the book Good Strategy, Bad Strategy, this article organizes the difference between good and bad strategies through the lens of diagnosis, guiding policy, and coherent actions.
Why and When to Write an Architecture Strategy
Develop architecture strategies to eliminate ad-hoc technology decisions and establish technology standards across teams.
Practical Techniques for Building System Architecture
A review of Practical Techniques for Building System Architecture. A practical guide for engineers doing architecture design in the field. Where the prior book focused on why, this one covers how, from requirements definition to logical and physical design and documentation through views, introducing concrete techniques useful on the ground.
Principles of Building System Architecture: Three Mindsets IT Architects Should Have
A review of Principles of Building System Architecture. A must-read if you are involved in architecture design. Beyond technical solutions, it systematically articulates the whole design process, from the definition and framing of architecture to engaging stakeholders and design techniques.
Considering the Shelf Life of Design
Consider design shelf life across business, organization, product, and technical perspectives. Balance constraints and trade-offs.
Things to Consider When Writing Architecture Documents
An article on what to keep in mind when writing architecture documents, which play an important role in system design. Rather than a mere listing of design information, it explains how to write them as material that explains the validity of a design to stakeholders, builds consensus, and guides readers to understanding and agreement.
Optimal Architecture Strategy for Requirements
A review of a book on requirement-optimal architecture strategy. It covers implementing architecture through domain-driven design once you understand the business strategy, devoting many pages to practical DDD and architecture implementation patterns, including why aiming for microservices from the start is hard.
How to Split a Large Monolith? - Lessons from Software Architecture Hard Parts
This article organizes useful points for considering service division from a monolith, based on chapters 1 to 4 of 'Software Architecture: The Hard Parts'.
Considering Architecture Strategy
Understand architecture strategy as systematic policy for building and evolving systems, covering vision, principles, and scalability planning.