SOAPatterns.org

• Overview
  • Introduction
  • History
  • Acknowledgements
  • Candidate Patterns
  • What is SOA
  • Press Releases
    • Press Release #1
    • Press Release #2
    • Press Release #3
• Design Patterns (alphabetical)
  • Overview
  • Agnostic Capability
  • Agnostic Context
  • Agnostic Sub-Controller
  • Asynchronous Queuing
  • Atomic Service Transaction
  • Augmented Protocols
  • Brokered Authentication
  • Canonical Expression
  • Canonical Protocol
  • Canonical Resources
  • Canonical Schema
  • Canonical Versioning
  • Capability Composition
  • Capability Recomposition
  • Compatible Change
  • Compensating Service Transaction
  • Composition Autonomy
  • Concurrent Contracts
  • Containerization
  • Content Negotiation
  • Contract Centralization
  • Contract Denormalization
  • Cross-Domain Utility Layer
  • Data Confidentiality
  • Data Format Transformation
  • Data Model Transformation
  • Data Origin Authentication
  • Decomposed Capability
  • Decoupled Contract
  • Direct Authentication
  • Distributed Capability
  • Domain Inventory
  • Dual Protocols
  • Endpoint Redirection
  • Enterprise Inventory
  • Entity Abstraction
  • Entity Linking
  • Event-Driven Messaging
  • Exception Shielding
  • File Gateway
  • Functional Decomposition
  • Idempotent Capability
  • Intermediate Routing
  • Inventory Endpoint
  • Legacy Wrapper
  • Lightweight Endpoint
  • Logic Centralization
  • Message Screening
  • Messaging Metadata
  • Metadata Centralization
  • Micro Task Abstraction
  • Microservice Deployment
  • Multi-Channel Endpoint
  • Non-Agnostic Context
  • Partial State Deferral
  • Partial Validation
  • Policy Centralization
  • Process Abstraction
  • Process Centralization
  • Protocol Bridging
  • Proxy Capability
  • Redundant Implementation
  • Reference Data Centralization
  • Reliable Messaging
  • Reusable Contract
  • Rules Centralization
  • Schema Centralization
  • Service Agent
  • Service Callback
  • Service Data Replication
  • Service Decomposition
  • Service Encapsulation
  • Service Façade
  • Service Grid
  • Service Instance Routing
  • Service Layers
  • Service Messaging
  • Service Normalization
  • Service Perimeter Guard
  • Service Refactoring
  • State Messaging
  • State Repository
  • Stateful Services
  • Termination Notification
  • Trusted Subsystem
  • UI Mediator
  • Utility Abstraction
  • Validation Abstraction
  • Version Identification
• Design Patterns (by category)
  • Foundational Inventory Patterns
    • Canonical Protocol
    • Canonical Schema
    • Domain Inventory
    • Enterprise Inventory
    • Logic Centralization
    • Service Layers
    • Service Normalization
  • Logical Inventory Layer Patterns
    • Entity Abstraction
    • Micro Task Abstraction
    • Process Abstraction
    • Utility Abstraction
  • Inventory Centralization Patterns
    • Policy Centralization
    • Process Centralization
    • Rules Centralization
    • Schema Centralization
  • Inventory Implementation Patterns
    • Augmented Protocols
    • Canonical Resources
    • Cross-Domain Utility Layer
    • Dual Protocols
    • Inventory Endpoint
    • Service Grid
    • State Repository
    • Stateful Services
  • Inventory Governance Patterns
    • Canonical Expression
    • Canonical Versioning
    • Metadata Centralization
  • Foundational Service Patterns
    • Agnostic Capability
    • Agnostic Context
    • Functional Decomposition
    • Non-Agnostic Context
    • Service Encapsulation
  • Service Implementation Patterns
    • Containerization
    • Microservice Deployment
    • Partial State Deferral
    • Partial Validation
    • Redundant Implementation
    • Reference Data Centralization
    • Service Data Replication
    • Service Façade
    • UI Mediator
  • Service Security Patterns
    • Exception Shielding
    • Message Screening
    • Service Perimeter Guard
    • Trusted Subsystem
  • Service Contract Design Patterns
    • Concurrent Contracts
    • Contract Centralization
    • Contract Denormalization
    • Decoupled Contract
    • Validation Abstraction
  • Legacy Encapsulation Patterns
    • File Gateway
    • Legacy Wrapper
    • Multi-Channel Endpoint
  • Service Governance Patterns
    • Compatible Change
    • Decomposed Capability
    • Distributed Capability
    • Proxy Capability
    • Service Decomposition
    • Service Refactoring
    • Termination Notification
    • Version Identification
  • Capability Composition Patterns
    • Capability Composition
    • Capability Recomposition
  • Service Messaging Patterns
    • Asynchronous Queuing
    • Event-Driven Messaging
    • Intermediate Routing
    • Messaging Metadata
    • Reliable Messaging
    • Service Agent
    • Service Callback
    • Service Instance Routing
    • Service Messaging
    • State Messaging
  • Composition Implementation Patterns
    • Agnostic Sub-Controller
    • Atomic Service Transaction
    • Compensating Service Transaction
    • Composition Autonomy
  • Service Interaction Security Patterns
    • Brokered Authentication
    • Data Confidentiality
    • Data Origin Authentication
    • Direct Authentication
  • Transformation Patterns
    • Data Format Transformation
    • Data Model Transformation
    • Protocol Bridging
  • REST-inspired Patterns
    • Content Negotiation
    • Endpoint Redirection
    • Entity Linking
    • Idempotent Capability
    • Lightweight Endpoint
    • Reusable Contract
• Compound Patterns
  • Overview
  • Canonical Schema Bus
  • Enterprise Service Bus
  • Federated Endpoint Layer
  • Official Endpoint
  • Orchestration
  • Service Broker
  • Three-Layer Inventory
  • Uniform Contract
• Microservice Patterns
• Big Data Patterns
• Cloud Computing Patterns
• SOACP
  • Home
  • Matrix
  • Certifications
  • Courses
  • Exams
  • Study Kits
  • eLearning Study Kits
  • Workshops
  • Licensing
  • Online Store

Three-Layer Inventory (Erl)

Joint application of Utility Abstraction, Entity Abstraction, and Process Abstraction.

This compound pattern is simply comprised of the combined application of the three service layer patterns. Three-Layer Inventory exists because the combined application of these three patterns results in common layers of abstraction that have been proven to complement and support each other by establishing services with flexible variations of agnostic and non-agnostic functional contexts.

The joint application of Entity Abstraction, Process Abstraction, Utility Abstraction results in Three-Layer Inventory.

This pattern is covered in SOACP Module 4: Fundamental SOA Analysis & Modeling with Services & Microservices.

For more information regarding the SOA Certified Pofessional (SOACP) curriculum,
visit www.arcitura.com/soa.