Figure A-1 summarizes the pattern-analysis scoring for each of the
architecture patterns described in this report. This summary will
help you determine which pattern might be best for your situation.
For example, if your primary architectural concern is scalability, you
can look across this chart and see that the event-driven pattern,
microservices pattern, and space-based pattern are probably good
architecture pattern choices. Similarly, if you choose the layered
architecture pattern for your application, you can refer to the chart
to see that deployment, performance, and scalability might be risk
areas in your architecture.
45
图A-1 总结了在这个报告中，对于架构模式的每部分进行的模式分析所产生的影响。这个总结帮助你确定哪些模式可能是最适合你的情况。例如,如果你的架构模式重点是可伸缩性，你可以在这个图表看看事件驱动模式,microservices模式,和基于空间模式，这些对于你来说可能是很好的架构模式的选择。同样的,如果你的程序注重的是分层架构模式,你可以参考图看到部署、性能和可伸缩性的在你的架构中所存在的风险。
While this chart will help guide you in choosing the right pattern,
there is much more to consider when choosing an architecture pattern.
You must analyze all aspects of your environment, including
infrastructure support, developer skill set, project budget, project
deadlines, and application size (to name a few). Choosing the right
architecture pattern is critical, because once an architecture is in
place, it is very hard (and expensive) to change
同时这个图表将指导你选择正确的模式,
因为在选择一种架构模式的时候，有更多的需要考虑。
你必须分析你的环境的各个方面,包括
基础设施的支持,开发人员技能,项目预算,项目
最后期限,和应用程序大小(等等)。选择正确的
架构模式是至关重要的,因为一旦一个架构
被确定了就很难改变。
Mark Richards is an experienced, hands-on software architect
involved in the architecture, design, and implementation of microservices
architectures, service-oriented architectures, and distributed
systems in J2EE and other technologies.
He has been in the
software industry since 1983 and has significant experience and
expertise in application, integration, and enterprise architecture.
Mark served as the president of the New England Java Users Group
from 1999 through 2003.
He is the author of numerous technical books and videos, including Software Architecture Fundamentals
(O’Reilly video), Enterprise Messaging (O’Reilly video), Java
Message Service, 2nd Edition (O’Reilly), and a contributing author
to 97 Things Every Software Architect Should Know (O’Reilly).
Mark has a master’s degree in computer science and numerous
architect and developer certifications from IBM, Sun, The Open
Group, and BEA.
He is a regular conference speaker at the No
Fluff Just Stuff (NFJS) Symposium Series and has spoken at more
than 100 conferences and user groups around the world on a variety
of enterprise-related technical topics.
When he is not working,
Mark can usually be found hiking in the White Mountains or
along the Appalachian Trail.
Mark•Richards是一位有实际经验的软件架构师，他参与架构、设计和实施microservices
体系结构、面向服务的体系结构和在J2EE中的分布式
系统和其他技术。自1983年以来，他一直从事软件行业,有大量的经验和专业知识在应用、集成和企业架构方面。
Mark从1999年到2003担任新英格兰Java用户组的主席。
他是许多技术书籍和视频的作者,包括软件架构基础(O‘Reilly视频)、企业消息传递(O'Reilly视频),《Java
消息服务，第二版》(O'Reilly)和《软件架构师应该知道的97件事》(O'Reilly)的特约作者。
Mark有一个计算机科学硕士学位和很多从IBM、Sun、开放
集团和BEA获得的架构师和开发人员认证。
他是Fluff Just Stuff(NFJS)研讨会系列的一个不定期会议议长
,并且超过100多次在世界各地的公益的会议和用户组上围绕技术主题
发言。当他不工作时,Mark通常会在白色山脉或阿帕拉契山径徒步旅行。
Copyright© 2013-2019