SOA Patterns | Design Patterns | Process Centralization


SOA Patterns > Inventory Centralization Patterns > Process Centralization
Home > Design Patterns > Process Centralization

Process Centralization (Erl)

How can abstracted business process logic be centrally governed?

Process Centralization

Problem

When business process logic is distributed across independent service implementations, it can be problematic to extend and evolve.

Solution

Logic representing numerous business processes can be deployed and governed from a central location.

Application

Middleware platforms generally provide the necessary orchestration technologies to apply this pattern.

Impacts

Significant infrastructure and architectural changes are imposed when the required middleware is introduced.

Architecture

Inventory, Composition

Process Centralization: Task services can continue to be implemented as separate Web services, but as part of an orchestration platform their collective business process logic is centrally located and governed (resulting in 'orchestrated' task services).

Task services can continue to be implemented as separate Web services, but as part of an orchestration platform their collective business process logic is centrally located and governed (resulting in “orchestrated” task services).


Module 7: Advanced SOA Design & Architecture with Services & Microservices

This pattern is covered in SOACP Module 7: Advanced SOA Design & Architecture with Services & Microservices.

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

SOA Design Patterns

This page contains excerpts from:

SOA Design Patterns by Thomas Erl

(ISBN: 0136135161, Hardcover, Full-Color, 400+ Illustrations, 865 pages)

For more information about this book, visit www.arcitura.com/books.