Patterns of Enterprise Application Architecture
Martin Fowler

ISBN-10: 0321127420
ISBN-13: 9780321127426

Publisher: Addison-Wesley Professional
Copyright: 2003
Format: Cloth; 560 pp
Published: 11/05/2002

Suggested retail price: $64.99
Buy from myPearsonStore

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.

A handbook for enterprise system developers guiding them through the intricacies and lessons learned in application development.

° The latest book from noted technology guru Martin Fowler

° Provides proven solutions to the everyday problems facing information systems developers

° Patterns are supported by code examples, in both Java and C#



Preface.

Who This Book Is For.

Acknowledgements.

Colophon.



Introduction.

Architecture.

Enterprise Applications.

Kinds of Enterprise Application.

Thinking About Performance.

Patterns.

The Structure of the Patterns.

Limitations of These Patterns.

I. THE NARRATIVES.

1. Layering.

The Evolution of Layers in Enterprise Applications.

The Three Principal Layers.

Choosing Where to Run Your Layers.

2. Organizing Domain Logic.

Making a Choice.

Service Layer.

3. Mapping to Relational Databases.

Architectural Patterns.

The Behavioral Problem.

Reading in Data

Structural Mapping Patterns.

Mapping Relationships.

Inheritance.

Building the Mapping.

Double Mapping.

Using Metadata.

Database Connections.

Some Miscellaneous Points.

Further Reading.

4. Web Presentation.

View Patterns.

Input Controller Patterns.

Further Reading.

5. Concurrency (by Martin Fowler and David Rice).

Concurrency Problems.

Execution Contexts.

Isolation and Immutability.

Optimistic and Pessimistic Concurrency Control.

Preventing Inconsistent Reads.

Deadlocks.

Transactions.

ACID.

Transactional Resources.

Reducing Transaction Isolation for Liveness.

Business and System Transactions.

Patterns for Offline Concurrency Control.

Application Server Concurrency.

Further Reading.

6. Session State.

The Value of Statelessness.

Session State.

Ways to Store Session State.

7. Distribution Strategies.

The Allure of Distributed Objects.

Remote and Local Interfaces.

Where You Have to Distribute.

Working with the Distribution Boundary.

Interfaces for Distribution.

8. Putting it all Together.

Starting With the Domain Layer.

Down to the Data Source.

Data Source for Transaction Script.

Data Source Table Module (125).

Data Source for Domain Model (116).

The Presentation Layer.

Some Technology-Specific Advice.

Java and J2EE.

.NET.

Stored Procedures.

Web Services.

Other Layering Schemes.

II. THE PATTERNS.

9. Domain Logic Patterns.

Transaction Script.

How It Works.

When to Use It.

The Revenue Recognition Problem.

Example: Revenue Recognition (Java).

Domain Model.

How It Works.

When to Use It.

Further Reading.

Example: Revenue Recognition (Java).

Table Module.

How It Works.

When to Use It.

Example: Revenue Recognition with a Table Module (C#).

Service Layer(by Randy Stafford).

How It Works.

When to Use It.

Further Reading.

Example: Revenue Recognition (Java).

10. Data Source Architectural Patterns.

Table Data Gateway.

How It Works.

When to Use It.

Further Reading.

Example: Person Gateway (C#).

Example: Using ADO.NET Data Sets (C#).

Row Data Gateway.

How It Works.

When to Use It.

Example: A Person Record (Java).

Example: A Data Holder for a Domain Object (Java).

Active Record.

How It Works.

When to Use It.

Example: A Simple Person (Java).

Data Mapper.

How It Works.

When to Use It.

Example: A Simple Database Mapper (Java).

Example: Separating the Finders (Java).

Example: Creating an Empty Object (Java).

11. Object-Relational Behavioral Patterns.

Unit of Work.

How It Works.

When to Use It.

Example: Unit of Work with Object Registration (Java) (by David Rice).

Identity Map.

How It Works.

When to Use It.

Example: Methods for an Identity Map (Java).

Lazy Load.

How It Works.

When to Use It.

Example: Lazy Initialization (Java).

Example: Virtual Proxy (Java).

Example: Using a Value Holder (Java).

Example: Using Ghosts (C#).

12. Object-Relational Structural Patterns.

Identity Field.

How It Works.

When to Use It.

Further Reading.

Example: Integral Key (C#).

Example: Using a Key Table (Java).

Example: Using a Compound Key (Java).

Foreign Key Mapping.

How It Works.

When to Use It.

Example: Single-Valued Reference (Java).

Example: Multitable Find (Java).

Example: Collection of References (C#).

Association Table Mapping.

How It Works.

When to Use It.

Example: Employees and Skills (C#).

Example: Using Direct SQL (Java).

Example: Using a Single Query for Multiple Employees (Java) (by Matt Foemmel and Martin Fowler).

Dependent Mapping.

How It Works.

When to Use It.

Example: Albums and Tracks (Java).

Embedded Value.

How It Works.

When to Use It.

Further Reading.

Example: Simple Value Object (Java).

Serialized LOB.

How It Works.

When to Use It.

Example: Serializing a Department Hierarchy in XML (Java).

Single Table Inheritance.

How It Works.

When to Use It.

Example: A Single Table for Players (C#).

Loading an Object from the Database.

Class Table Inheritance.

How It Works.

When to Use It.

Further Reading.

Example: Players and Their Kin (C#).

Concrete Table Inheritance.

How It Works.

When to Use It.

Example: Concrete Players (C#).

Inheritance Mappers.

How It Works.

When to Use It.

13. Object-Relational Metadata Mapping Patterns.

Metadata Mapping.

How It Works.

When to Use It.

Example: Using Metadata and Reflection (Java).

Query Object.

How It Works.

When to Use It.

Further Reading.

Example: A Simple Query Object (Java).

Repository (by Edward Hieatt and Rob Mee).

How It Works.

When to Use It.

Further Reading.

Example: Finding a Person's Dependents (Java).

Example: Swapping Repository Strategies (Java).

14. Web Presentation Patterns.

Model View Controller.

How It Works.

When to Use It.

Page Controller.

How It Works.

When to Use It.

Example: Simple Display with a Servlet Controller and a JSP View (Java).

Example: Using a JSP as a Handler (Java).

Example: Page Handler with a Code Behind (C#).

Front Controller.

How It Works.

When to Use It.

Further Reading.

Example: Simple Display (Java).

Template View.

How It Works.

When to Use It.

Example: Using a JSP as a View with a Separate Controller (Java).

Example: ASP.NET Server Page (C#).

Transform View.

How It Works.

When to Use It.

Example: Simple Transform (Java).

Two Step View.

How It Works.

When to Use It.

Example: Two Stage XSLT (XSLT).

Example: JSP and Custom Tags (Java).

Application Controller.

How It Works.

When to Use It.

Further Reading.

Example: State Model Application Controller (Java).

15. Distribution Patterns.

Remote Facade.

How It Works.

When to Use It.

Example: Using a Java Session Bean as a Remote Facade (Java).

Example: Web Service (C#).

Data Transfer Object.

How It Works.

When to Use It.

Further Reading.

Example: Transferring Information about Albums (Java).

Example: Serializing Using XML (Java).

16. Offline Concurrency Patterns.

Optimistic Offline Lock (by David Rice).

How It Works.

When to Use It.

Example: Domain Layer with Data Mappers (165) (Java).

Pessimistic Offline Lock (by David Rice).

How It Works.

When to Use It.

Example: Simple Lock Manager (Java).

Coarse-Grained Lock (by David Rice and Matt Foemmel).

How It Works.

When to Use It.

Example: Shared Optimistic Offline Lock (416) (Java).

Example: Shared Pessimistic Offline Lock (426) (Java).

Example: Root Optimistic Offline Lock (416) (Java).

Implicit Lock (by David Rice).

How It Works.

When to Use It.

Example: Implicit Pessimistic Offline Lock (426) (Java).

17. Session State Patterns.

Client Session State.

How It Works.

When to Use It.

Server Session State.

How It Works.

When to Use It.

Database Session State.

How It Works.

When to Use It.

18. Base Patterns.

Gateway.

How It Works.

When to Use It.

Example: A Gateway to a Proprietary Messaging Service (Java).

Mapper.

How It Works.

When to Use It.

Layer Supertype.

How It Works.

When to Use It.

Example: Domain Object (Java).

Separated Interface.

How It Works.

When to Use It.

Registry.

How It Works.

When to Use It.

Example: A Singleton Registry (Java).

Example: Thread-Safe Registry (Java) (by Matt Foemmel and Martin Fowler).

Value Object.

How It Works.

When to Use It.

Money.

How It Works.

When to Use It.

Example: A Money Class (Java) (by Matt Foemmel and Martin Fowler).

Special Case.

How It Works.

When to Use It.

Further Reading.

Example: A Simple Null Object (C#).

Plugin (by David Rice and Matt Foemmel).

How It Works.

When to Use It.

Example: An Id Generator (Java).

Service Stub (by David Rice).

How It Works.

When to Use It.

Example: Sales Tax Service (Java).

Record Set.

How It Works.

When to Use It.

References

Index. 0321127420T10162002

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.



0321127420AB07242003

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


    • 0321127420B10152002

    View a Sample Chapter PDF: /samplechapter/0321127420.pdf

    Pearson Higher Education offers special pricing when you choose to package your text with other student resources. If you're interested in creating a cost-saving package for your students, contact your Pearson Higher Education representative for pricing and ordering information.

    This title is a member of the Addison-Wesley Signature Series, which also contains the titles below . You can also visit the Addison-Wesley Signature Series page.

      Luke Hohmann borrows from his extensive experience managing successful enterprise software projects to provide practical wisdom on creating and sustaining winning software solutions. This book teaches students how to build a software architecture that aligns with a customer's overall business goals and helps students grasp the business ramifications of their decisions. These are two important aspects for any student to take away from a software engineering course as these skills will be vitally important when they enter the workforce.

    • 0201775948Beyond Software Architecture: Creating and Sustaining Winning Solutions
      Hohmann
      © 2003 | Addison-Wesley Professional | Paper; 352 pages | Instock
      ISBN-10: 0201775948 | ISBN-13: 9780201775945
      Brief Description | Buy from myPearsonStore

    • 0321336380Continuous Integration: Improving Software Quality and Reducing Risk
      Duvall, Matyas & Glover
      © 2007 | Addison-Wesley Professional | Paper; 336 pages | Instock
      ISBN-10: 0321336380 | ISBN-13: 9780321336385
      Buy from myPearsonStore

    • 0321413091Implementation Patterns
      Beck
      © 2008 | Addison-Wesley Professional | Paper; 176 pages | Instock
      ISBN-10: 0321413091 | ISBN-13: 9780321413093
      Buy from myPearsonStore

    • 0321437381Implementing Lean Software Development: From Concept to Cash
      Poppendieck & Poppendieck
      © 2007 | Addison-Wesley Professional | Paper; 304 pages | Instock
      ISBN-10: 0321437381 | ISBN-13: 9780321437389
      Buy from myPearsonStore

      • 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.

    • 0321127420Patterns of Enterprise Application Architecture
      Fowler
      © 2003 | Addison-Wesley Professional | Cloth; 560 pages | Instock
      ISBN-10: 0321127420 | ISBN-13: 9780321127426
      Brief Description | Buy from myPearsonStore

    • 0321293533Refactoring Databases: Evolutionary Database Design
      Ambler & Sadalage
      © 2006 | Addison-Wesley Professional | Cloth; 384 pages | Instock
      ISBN-10: 0321293533 | ISBN-13: 9780321293534
      Buy from myPearsonStore

    • 0321503635Refactoring HTML: Improving the Design of Existing Web Applications
      Harold
      © 2008 | Addison-Wesley Professional | Cloth; 368 pages | Instock
      ISBN-10: 0321503635 | ISBN-13: 9780321503633
      Buy from myPearsonStore

      • With the highly anticipated Refactoring to Patterns, Joshua Kerievsky has changed our approach to design by forever uniting patterns with the evolutionary process of refactoring.

      Intended for the more experienced student, this book introduces the theory and practice of pattern-directed refactorings: sequences of low-level refactorings that allow designers to safely move designs to, towards, or away from pattern implementations. Using code from real-world projects, Kerievsky documents the thinking and steps underlying over two dozen pattern-based design transformations. Along the way he offers insights into pattern differences and how to implement patterns in the simplest possible ways.

    • 0321213351Refactoring to Patterns
      Kerievsky
      © 2005 | Addison-Wesley Professional | Cloth; 400 pages | Instock
      ISBN-10: 0321213351 | ISBN-13: 9780321213358
      Brief Description | Buy from myPearsonStore

      • Test-driven development (TDD) is a new approach to application development that is designed to eliminate the fear often associated with building software. Admittedly, some fear is healthy (often viewed as a conscience that tells programmers to “be careful!”), but the author believes that programmers build better software when they have the freedom to be creative. By building tests before coding begins, programmers ensure the success of their application from the outset. Students are more likely to achieve positive results with TDD. The author's example-driven approach also teaches students to be better communicators, and encourages team members to seek out constructive criticism.

    • 0321146530Test Driven Development: By Example
      Beck
      © 2003 | Addison-Wesley Professional | Paper; 240 pages | Instock
      ISBN-10: 0321146530 | ISBN-13: 9780321146533
      Brief Description | Buy from myPearsonStore

      • The concept of user stories has its roots as one of the main tenets of Extreme

      Programming. In simple terms, user stories represent an effective means of

      gathering requirements from the customer (roughly akin to use cases). This

      book describes user stories and demonstrates how they can be used to properly

      plan, manage, and test software development projects. The book highlights

      both successful and unsuccessful implementations of the concept, and provides

      sets of questions and exercises that drive home its main points. After absorbing

      the lessons in this book, readers will be able to introduce user stories in their

      organizations as an effective means of determining precisely what is required of

      a software application.

    • 0321205685User Stories Applied: For Agile Software Development
      Cohn
      © 2004 | Addison-Wesley Professional | Paper; 304 pages | Instock
      ISBN-10: 0321205685 | ISBN-13: 9780321205681
      Brief Description | Buy from myPearsonStore

    • 0131495054xUnit Test Patterns: Refactoring Test Code
      Meszaros
      © 2007 | Addison-Wesley Professional | Cloth; 944 pages | Instock
      ISBN-10: 0131495054 | ISBN-13: 9780131495050
      Buy from myPearsonStore

    Pearson Higher Education offers special pricing when you choose to package your text with other student resources. If you're interested in creating a cost-saving package for your students contact your Pearson Higher Education representative.


    Copyright ©2008 Pearson Education. All rights reserved. Legal Notice | Privacy Policy | Permissions