880
筆記：Driving Architectural Simplicity - The Value, Challenge, and Practice of Simple Solutions
感覺這篇文章對於為什麼，以及如何簡化架構說的很透。
開篇：
Key Takeaways
Simple architectures are easier to communicate, build, deploy, operate, and evolve.
Architectural simplicity is not easily encapsulated by one type of model or practice. Several practices can be applied in combination to drive simplicity.
Agile practices stress simplicity. Architectural complexity can occur based on many factors such as design ability and focus, technology evolution, and organizational structure.
Defining simple architectures is difficult and takes a concerted, continuous effort.
Simplicity is a great virtue but it requires hard work to achieve it and education to appreciate it. And to make matters worse: complexity sells better. - Edsger W. Dijkstra (1984)
簡化架構的好處（Benefits of Architectural Simplicity ）:
First, simple architectures are easier to communicate. Communication includes both documentation and comprehension. A simple architecture can be documented with a smaller model and fewer drawings/annotations which would lead to improved comprehension by stakeholders. Comprehension is critical for shared understanding, which some define as the architecture (from Martin’s Fowler’s seminal Who Needs an Architect?). A shared understanding is critical to maintaining alignment across teams and team members, and ensuring an efficient implementation.
Second, simple architectures are often easier to implement. They have fewer moving parts, fewer interactions, and fewer opportunities for failure. However, this isn’t always the case. Sometimes it may take more time to implement a simple architecture given the number of try/fail/learn iterations that go into the process of identifying a truly simple design.
Third, simple architectures are easier to deploy and operate. Fewer moving parts aligns to a more straightforward deployment. Then once in production, simple architectures are more easily scaled and monitored. Another great quote from Edsger Dijkstra is "Simplicity is a prerequisite for reliability."
Fourth, simple architectures are easier to modify and evolve. Simplicity is a key principle of Agile practices and a rule for XP development. Simple architectures allow the development team to be more productive since there is less complexity to track and fewer points of impact when making changes.
什麼是架構簡化（What is Architectural Simplicity? ）：
Strive for the Simplest Option
Apply YAGNI – You Aint’t Gonna Need It
Practice Parsimony
Avoid Premature Optimization
複雜的原因（Reasons for Complexity）
Complexity Sells
Developing is Fun
Keeping Up With The Joneses
Simple is Hard
Organizational Structure
實施簡化的建議（Recommendations for Driving Architectural Simplicity ）
Design Up Front
Design Throughout Delivery
Ask Questions, Often
Understand Decision Tradeoffs
Create Proof of Concepts
Communicate Effectively and Often
Embrace Minimum Viable
Make Architecture Everyone’s Responsibility
Be Continuously Obsessive
這篇文章寫的很容易理解，很多部分其實你看我整理的KeyNote就知道是什麼東西了，如果想詳細了解，文章鏈接如下：
https://www.infoq.com/articles/driving-architectural-simplicity?utm_source=infoq&utm_medium=popular_widget&utm_campaign=popular_content_list&utm_content=homepage
最後更新：2017-08-22 11:02:44