Enterprise Architectural Patterns

 An architectural pattern is a common standard for an architecture and solution to a problem. Unlike Design Patterns, an architectural pattern has a broader scope and can address big problems.  The architectural pattern address various issues of software engineering, such as computer hardware performance limitations, high availability and minimizing business risk. 

According to Martin Fowler, there Enterprise Architectural Patterns are broadly categorized into 

1. Domain Logic Patterns 

• Transaction Script
• Domain Model
• Table Module
• Service Layer

2. Data Source Architectural Patterns

• Table Data Gateway
• Row Data Gateway
• Active Record
• Data Mapper

3. Object Relational Behavioral Patterns 

• Unit of Work
• Identity Map
• Lazy Load

4. Object Relational Structural Patterns

• Identity Field
• Foreign Key Mapping
• Association Table Mapping
• Dependent Mapping
• Embedded Value
• Serialized LOB
• Single Table Inheritance
• Class Table Inheritance
• Concrete Table Inheritance
• Inheritance Mappers

5. Object Relational Metadata Mapping Patterns

• Metadata Mapping
• Query Object
• Repository

6. Web Presentation Patterns

• Model View Controller
• Page Controller
• Front Controller
• Template View
• Transform View
• Two-step View
• Application Controller

7. Distribution Patterns

• Remote Facade
• Data Transfer Object

8. Offline Concurrency Patterns

• Optimistic Offline Lock
• Pessimistic Offline Lock
• Coarse Grained Lock
• Implicit Lock

9. Session State Patterns

• Client Session State
• Server Session State
• Database session State

10. Base Patterns

• Geteway
• Mapper
• Layer Supertype
• Separated Interface
• Registry
• Value Object
• Money
• Special Case
• Plugin 
• Service Stub
• Record Set 

I would edit this article with all the links when I am complete in writing implementation of each of those. If you have contributed anyone of these patterns, please go ahead and put the links.