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
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.
花了蛮久的时间每天抽出半个小时终于从头到尾读完了。总的来说,这本书写得非常系统,从web层的实现到后端数据源的选择,几乎无所不包。虽然某些内容明显已经有点过时了,但其思考、分析、解决问题的方式还是非常好的。特别是对那些只知道如何使用Spring、Hibernate、Struts架...
评分2007年以前读的话帮助会很大。 书中的很多内容,如三层架构、持久化与业务逻辑分离等现在已经成为了业界常识,但是本书的地位还是值的肯定得。 如果没有读过其他比较新的设计思想,用这本书用来补充自己对架构发展上方面认识还是很有帮助的。
评分花了蛮久的时间每天抽出半个小时终于从头到尾读完了。总的来说,这本书写得非常系统,从web层的实现到后端数据源的选择,几乎无所不包。虽然某些内容明显已经有点过时了,但其思考、分析、解决问题的方式还是非常好的。特别是对那些只知道如何使用Spring、Hibernate、Struts架...
评分1 本书几乎涉及到架构的所有方面,从服务层,逻辑层到数据层,到接口,到各种模式。无所不包。 2 书有些年头,但内容真的很经典。作者很善于把日常中的思路归纳整理成一个模式,并且相互比较。 3 书不但有理论,还有代码实例和运用场景。但如果没有长期的代码经验,看上去会有...
你可以相信 Martin
评分重读之后感觉之前像没读过一样, 果然经验不一样了啊.
评分重读之后感觉之前像没读过一样, 果然经验不一样了啊.
评分确切的讲,是读过Part I: The Narriatives. 后面的内容是企业架构模式的详述,我觉得最好是找几个典型的框架源代码对照着读效果比较好。这本书完成的时间是2002年,现在读这本书的时候不得不赞叹教父Martin Fowler的前瞻性。虽然由于技术的快速发展,有些内容已经过时了,比如EJB2,但本书把些数据库对象关系、事务、并发、领域模型、MVC等讲得很深入。 读教父的书你不得很佩服他的洞察力,他非常善于从司空见惯的日常现象中发现规律并且据此准确得预测未来。
评分重读之后感觉之前像没读过一样, 果然经验不一样了啊.
本站所有内容均为互联网搜索引擎提供的公开搜索信息,本站不存储任何数据与内容,任何内容与数据均与本站无关,如有需要请联系相关搜索引擎包括但不限于百度,google,bing,sogou 等
© 2025 book.wenda123.org All Rights Reserved. 图书目录大全 版权所有