Science current events, science news articles, research and discoveries.
Top science news articles and science current events stories from the past week.
Science Current Events Resources
Science Current Events and Science News RSS Feeds
Earth, Life and Space Science News and Current Events RSS Feeds.
|
 |
 |
 |
| View Larger Image | Patterns of Enterprise Application Architecture (Addison-Wesley Signature Series) by Martin Fowler
| | List Price: | $64.99 | | Price: | $51.99 | | You Save: | $13.00 (20%) |  | | Available: | Usually ships in 24 hours |  | |  | | Sales Rank: | 5985 | | Studio: | Addison-Wesley Professional |  | | Binding: | Hardcover | | Number Of Pages: | 560 | | Publication Date: | November 15, 2002 | | Publisher: | Addison-Wesley Professional |
| |
ACCESSORIES |
| |
|
EDITORIAL REVIEWS | Product Description Noted software engineering expert, Martin Fowler, turns his attention to enterprise application development. He helps professionals understand the complex--yet critical--aspects of architecture. Enables the reader to make proper choices when faced with a difficult design decision. |
CUSTOMER REVIEWS (Average Customer Rating: 4.5 based on 54 reviews)
| Misses out on the important patterns  This book is a complete beginner's handbook for enterprise patterns.
1) The "Mapping to Relational Database Patterns" section discusses patterns that are completely intuitive. I recall logically coming to this conclusions when I started programming in Visual Basic in 99. Nothing new in this section.
2) The "Concurrency" section is criminal in nature and assumes that the application runs on high-cost server. Process-per-session? Thread-per-request? Come on!! Has the author missed out on the Reactor, Proactor and Active Object patterns (he does reference ACE but only as a reference). These patterns have been recognized as not scalable in the late 90s.
3)The distribution patterns are clearly incomplete and desire a lot of details.
If you're just starting out,as a System Architect :-), you'll find this useful. Otherwise, use MSDN or ACE for enterprise patterns. August 07, 2007 | | Must have reference for all developers  Even if you don't do "Enterprise Application" development, this book is a must have in your library. If you have been developing for more than a couple of years and you haven't seen 1/2 of the patterns in this book, then you are probably doing something wrong and this book could greatly help you.
Even if you do know 1/2 or more of the patterns in this book it is a great reference to the details of these patterns. Unless you are a Sophomore Software Engineering Student I'd recommend this book over the GoF book. Gof is a must have too, but if you can only have one. Get this one! July 16, 2007 | | Must read  This is a must read book if you are a developer, architect or in anyway related to technology. April 04, 2007 | | Great reference for building business apps  For me, this book is an invaluable reference for building business apps.
Want help choosing a framework? Want some guidance for solving common business problems? These patterns help solve these kinds of problems.
NOTE: I have tried to find other sources for these patterns, and I have only found Fowlers website, which is really only a summary and recommends purchasing the book.
This book has examples in both Java and C#. You can certainly use these patterns in .NET.
Under .NET you are not actually forced to use the Table Model. I think the purpose of this book is to help you realize this.
There are frameworks for .NET that use the Domain Model and Data Mapper patterns, but you would never know this unless you were familiar with the patterns in this book.
For me, reading this book didn't allow me to write new code, but it did allow me to understand my choice to use a particular framework/technique over another. March 12, 2007 | | Educates you on Enterprise Architecture  As a newcomer to enterprise architecture this book educated me on possibilities for decisions to be made in designing an enterprise architect. It will also give you a language for describing existing characteristics of an existing enterprise application which may use some combination of the patterns describe in this book. The discussion of where to keep session state for a webapp was particularly helpful to me. March 09, 2007 | |
SIMILAR PRODUCTS |
| | Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions (Addison-Wesley Signature Series) by Gregor Hohpe, Bobby Woolf
| | Domain-Driven Design: Tackling Complexity in the Heart of Software by Eric Evans
| | Design Patterns: Elements of Reusable Object-Oriented Software (Addison-Wesley Professional Computing Series) by Erich Gamma, Richard Helm, Ralph Johnson, John M. Vlissides
| | Refactoring: Improving the Design of Existing Code (Addison-Wesley Object Technology Series) by Martin Fowler, Kent Beck, John Brant, William Opdyke, Don Roberts
| | Head First Design Patterns (Head First) by Elisabeth Freeman, Eric Freeman, Bert Bates, Kathy Sierra
|
|
|
|
|