Martin Fowler 2003
From CSSEMediaWiki
(Difference between revisions)
Joey Scarr (Talk | contribs) m (→Update) |
m (Reverted edits by Ebybymic (Talk); changed back to last version by Joey Scarr) |
| (One intermediate revision by one user not shown) | |
Latest revision as of 03:11, 25 November 2010
Martin Fowler's architectural patterns book
Patterns of enterprise application architecture by Martin Fowler, 2003.
This is a must-have book for anyone working on "enterprise applications", which used to be known as "information systems", or (for old farts) "data processing". The patterns cover topics such as complex data, concurrency, persistence, distribution, and user interfaces.
The book is in two parts: Part 1 is a narrative that motivates and explains the patterns; part 2 is a catalogue.
The UML diagrams are [[1]].
Domain logic patterns
| Transaction script pattern | Organizes business logic by procedures where each procedure handles a single request from the presentation. |
| Domain model pattern | An object model of the domain that incorporates both behavior and data. |
| Table module pattern | A single instance that handles the business logic for all rows in a database table or view. |
| Service layer pattern | Defines an application's boundary with a layer of services that establishes a set of available operations and coordinates the application's response in each. |
Data source architectural patterns
| Table data gateway pattern | An object that acts as a Gateway to a database table. One instance handles all the rows in the table. |
| Row data gateway pattern | An object that acts as a Gateway to a single record in a data source. There is one instance per row. |
| Active record pattern | An object that wraps a row in a database table or view, encapsulates the database access, and adds domain logic on that data. |
| Data mapper pattern | A layer of Mappers that moves data between objects and a database while keeping them independent of each other and the mapper itself. |
Object-Relational Behavioral Patterns
| Unit of work pattern | Maintains a list of objects affected by a business transaction and coordinates the writing out of changes and the resolution of concurrency problems. |
| Identity map pattern | Ensures that each object gets loaded only once by keeping every loaded object in a map. Looks up objects using the map when referring to them. |
| Lazy load pattern | An object that doesn't contain all of the data you need but knows how to get it. |
Object-Relational Structural Patterns
| Identity field pattern | Saves a database ID field in an object to maintain identity between an in-memory object and a database row. |
| Foreign key mapping pattern | Maps an association between objects to a foreign key reference between tables. |
| Association table mapping pattern | Saves an association as a table with foreign keys to the tables that are linked by the association. |
| Dependent mapping pattern | Has one class perform the database mapping for a child class. |
| Embedded value pattern | Maps an object into several fields of another object's table. |
| Serialized lob pattern | Saves a graph of objects by serializing them into a single large object (LOB), which it stores in a database field. |
| Single table inheritance pattern | Represents an inheritance hierarchy of classes as a single table that has columns for all the fields of the various classes. |
| Class table inheritance pattern | Represents an inheritance hierarchy of classes with one table for each class. |
| Concrete table inheritance pattern | Represents an inheritance hierarchy of classes with one table per concrete class in the hierarchy. |
| Inheritance mappers pattern | A structure to organize database mappers that handle inheritance hierarchies. |
Object-Relational Metadata Mapping Patterns
| Metadata mapping pattern | Holds details of object-relational mapping in metadata. |
| Query object pattern | An object that represents a database query. |
| Repository pattern | Mediates between the domain and data mapping layers using a collection-like interface for accessing domain objects. |
Web Presentation Patterns
| Model view controller pattern | Splits user interface interaction into three distinct roles. |
| Page controller pattern | An object that handles a request for a specific page or action on a Web site. |
| Front controller pattern | A controller that handles all requests for a Web site. |
| Template view pattern | Renders information into HTML by embedding markers in an HTML page. |
| Transform view pattern | A view that processes domain data element by element and transforms it into HTML. |
| Two step view pattern | Turns domain data into HTML in two steps: first by forming some kind of logical page, then rendering the logical page into HTML. |
| Application controller pattern | A centralized point for handling screen navigation and the flow of an application. |
Distribution Patterns
| Remote facade pattern | Provides a coarse-grained facade on fine-grained objects to improve efficiency over a network. |
| Data transfer object pattern | An object that carries data between processes in order to reduce the number of method calls. |
Offline Concurrency Patterns
| Optimistic offline lock pattern | Prevents conflicts between concurrent business transactions by detecting a conflict and rolling back the transaction. |
| Pessimistic offline lock pattern | Prevents conflicts between concurrent business transactions by allowing only one business transaction at a time to access data. |
| Coarse grained lock pattern | Locks a set of related objects with a single lock. |
| Implicit lock pattern | Allows framework or layer supertype code to acquire offline locks. |
Session State Patterns
| Client session state pattern | Stores session state on the client. |
| Server session state pattern | Keeps the session state on a server system in a serialized form. |
| Database session state pattern | Stores session data as committed data in the database. |
Base Patterns
| Gateway pattern | An object that encapsulates access to an external system or resource. |
| Mapper pattern | An object that sets up a communication between two independent objects. |
| Layer supertype pattern | A type that acts as the supertype for all types in its layer. |
| Separated interface pattern | Defines an interface in a separate package from its implementation. |
| Registry pattern | A well-known object that other objects can use to find common objects and services. |
| Value object pattern | A small simple object, like money or a date range, whose equality isn't based on identity. |
| Money pattern | Represents a monetary value. |
| Special case pattern | A subclass that provides special behavior for particular cases. |
| Plugin pattern | Links classes during configuration rather than compilation. |
| Service stub pattern | Removes dependence upon problematic services during testing. |
| Record set pattern | An in-memory representation of tabular data. |
Update
Fowler is working on a new edition, which will merge in updated ideas from his analysis patterns book, Martin Fowler 1997. See more enterprise architecture.
