Patterns of Enterprise Application Architecture

Martin Fowler is an independent consultant who has applied objects to pressing business problems for more than a decade. He has consulted on systems in fields such as health care, financial trading, and corporate finance. His clients include Chrysler, Citibank, UK National Health Service, Andersen Consulting, and Netscape Communications. In addition, Fowler is a regular speaker on objects, the Unified Modeling Language, and patterns.

出版者:Addison-Wesley Professional

作者:Martin Fowler

页数:560

出版时间:2002-11-15

价格:USD 69.99

装帧:Hardcover

isbn号码:9780321127426

丛书系列:The Addison-Wesley Signature Series

图书标签:设计模式架构Martin_Fowler软件工程architecturepattern计算机编程

The practice of enterprise application development has benefited from the emergence of many new enabling technologies. Multi-tiered object-oriented platforms, such as Java and .NET, have become commonplace. These new tools and technologies are capable of building powerful applications, but they are not easily implemented. Common failures in enterprise applications often occur because their developers do not understand the architectural lessons that experienced object developers have learned. Patterns of Enterprise Application Architecture is written in direct response to the stiff challenges that face enterprise application developers. The author, noted object-oriented designer Martin Fowler, noticed that despite changes in technology--from Smalltalk to CORBA to Java to .NET--the same basic design ideas can be adapted and applied to solve common problems. With the help of an expert group of contributors, Martin distills over forty recurring solutions into patterns. The result is an indispensable handbook of solutions that are applicable to any enterprise application platform. This book is actually two books in one. The first section is a short tutorial on developing enterprise applications, which you can read from start to finish to understand the scope of the book's lessons. The next section, the bulk of the book, is a detailed reference to the patterns themselves. Each pattern provides usage and implementation information, as well as detailed code examples in Java or C#. The entire book is also richly illustrated with UML diagrams to further explain the concepts. Armed with this book, you will have the knowledge necessary to make important architectural decisions about building an enterprise application and the proven patterns for use when building them. The topics covered include * Dividing an enterprise application into layers * The major approaches to organizing business logic * An in-depth treatment of mapping between objects and relational databases * Using Model-View-Controller to organize a Web presentation * Handling concurrency for data that spans multiple transactions * Designing distributed object interfaces

读后感

这本书太老了；书中所讨论的问题，现在使用框架技术，都可以解决了。 现在有些指导意义的是，前几章，对于性能评估和分层的概念性的东西。 性能评估 * 响应时间， * 响应性 * 等待时间 * 吞吐率。 * 负载 * 负载敏感度 * 效率 * 系统容量 * 可伸缩性（垂直可伸缩性...  

尽管首先建立模型是一种合理的方法，但这个建议仅仅适用于短的迭代周期内。花费6个月的时间建立一个没有数据库的领域模型，并且决定一旦完成就持久化它，这是一件非常冒险的事情。危险在于，设计结果会因为迫切的性能问题而需要进行很多重构来修复。相反，应该为每一次迭代建造...  

该书非常前面简述了一个项目的架构，从前端到业务层，再到数据层，非常全面，层和层的关系，需要注意的问题，非常好！  

（打分只针对翻译） 正在读， 强烈建议买原版. 这版的翻译， 只是在“勉强能看”的程度. 很多专业名词的翻译让你云雾缭绕的， 比如把单例翻译成单子，还有什么“现场识别”， 听都没听说过的东西. 而且完全是字面翻译， 丝毫不考虑中文表达习惯和上下文， 经常需要反推英文去...  

这本书太老了；书中所讨论的问题，现在使用框架技术，都可以解决了。 现在有些指导意义的是，前几章，对于性能评估和分层的概念性的东西。 性能评估 * 响应时间， * 响应性 * 等待时间 * 吞吐率。 * 负载 * 负载敏感度 * 效率 * 系统容量 * 可伸缩性（垂直可伸缩性...  

用户评价

确切的讲，是读过Part I: The Narriatives. 后面的内容是企业架构模式的详述，我觉得最好是找几个典型的框架源代码对照着读效果比较好。这本书完成的时间是2002年，现在读这本书的时候不得不赞叹教父Martin Fowler的前瞻性。虽然由于技术的快速发展，有些内容已经过时了，比如EJB2，但本书把些数据库对象关系、事务、并发、领域模型、MVC等讲得很深入。 读教父的书你不得很佩服他的洞察力，他非常善于从司空见惯的日常现象中发现规律并且据此准确得预测未来。

如果说世上有什么神作，这就是。

如果说Rails是一棵树，这本书就是那片森林，以及滋养它们的土壤。

解答了我的很多对于best practice的困惑，不过很多的东西还是需要自己在project中去体会。

如果说Rails是一棵树，这本书就是那片森林，以及滋养它们的土壤。