What does this research mean for the field?

The Orchestration Domain-Centric Pattern (ODCP) reduces package count by 90%, technical users by 69%, and deployment time by 95% in enterprise integration platforms. Novelty: ClaimNovelty.NOVEL_FINDING. Consensus alignment: ConsensusAlignment.NEUTRAL.

What question did this study set out to answer?

To establish a vendor-agnostic orchestration topology that organizes integration artifacts by business domain semantics.

March 7, 2026Open Access

Orchestration Domain-Centric Pattern (ODCP): A Vendor-Agnostic Domain-Semantic Orchestration Topology for Enterprise Integration Platforms - v1.0

Key Points

To establish a vendor-agnostic orchestration topology that organizes integration artifacts by business domain semantics.
Developed Orchestration Domain-Centric Pattern (ODCP) with design principles for structuring artifacts.
Validated within SAP BTP Cloud Integration (CPI) by consolidating orchestration packages and users.
Utilized three structural invariants: Domain-Centric Package Consolidation, iFlow DNA naming, and Credential Governance.
Achieved a 90% reduction in orchestration package count from 39 to 4.
Reduced technical user count by 69%, from 39 to 12.
Decreased deployment time by 95% with successful processing of 1,499,869 requests.

Abstract

Orchestration Domain-Centric Pattern (ODCP) defines a vendor-agnostic structural topology for organizing integration orchestration artifacts by business domain semantics, rather than by system origin, vendor identity, or project boundary. Operating at the orchestration layer of enterprise integration platforms — where packages, integration flows, runtime artifacts, and technical credentials accumulate complexity over time — ODCP ensures that the same semantic vocabulary governing the API gateway façade propagates uninterrupted into the backend execution artifact. ODCP addresses three compounded anti-patterns present in virtually every large-scale integration landscape: Package Sprawl (orchestration artifacts grouped by vendor or project rather than domain) Integration Flow Naming Chaos (non-deterministic, non-machine-readable artifact identifiers) Technical User Blackout Risk (unsegmented credentials creating systemic failure during rotation events) It resolves all three through three structural invariants: Domain-Centric Package Consolidation with Package DNA Naming Convention, iFlow DNA deterministic naming, and Sub-Domain Tiered Credential Governance — turning package count, naming, and credential scope into stable, governable dimensions of the platform. The pattern was originally validated inside SAP BTP Cloud Integration (CPI) as the Package Domain-Centric Pattern (PDCP). In this validation, 39 orchestration packages were consolidated into 4 (↓90%), 39 technical users into 12 (↓69%), and deployment time was reduced by 95% — as part of a GDCR v6. 0 proof-of-concept processing 1, 499, 869 requests with 100% routing success and zero orchestration failures. ODCP generalizes PDCP into a vendor-agnostic organizational standard applicable to any orchestration platform supporting configurable artifact containers, deterministic naming, and segmented credentials — including SAP BTP CPI, MuleSoft Anypoint Platform, Azure Integration Services, AWS Step Functions, IBM App Connect, Boomi AtomSphere, Workato, Informatica IICS, Tibco BusinessWorks, and WSO2 Micro Integrator. ODCP is the third pillar of the Semantic Domain Integration Architecture (SDIA), composed with GDCR (Gateway Domain-Centric Routing — semantic gateway façade) and DDCR (Domain Driven Centric Router — deterministic 7-stage runtime resolution engine), forming an end-to-end semantic integration chain from human-readable API address to backend execution artifact. Together, these three DOI-published patterns establish a governance model in which business domain semantics are the permanent integration language and technology becomes background infrastructure. Companion Architecture: Gateway Domain-Centric Routing (GDCR) — DOI: 10. 5281/zenodo. 18582492. Keywords: Orchestration Governance, Package Sprawl, iFlow DNA, Integration Flow Naming Convention, Artifact Naming, Technical User Governance, Credential Segmentation, Blast Radius Control, Domain-Centric Architecture, Vendor-Agnostic Governance, SAP BTP Cloud Integration, PDCP, SDIA, Integration Artifact Management, Semantic Continuity License: Creative Commons Attribution 4. 0 International (CC BY 4. 0) USPTO Trademark Application: 99680660 — GDCR, DDCR, ODCPORCID: https: //orcid. org/0009-0009-9549-5862 Citation APA: Viana, R. L. H. (2026). Gateway Domain-Centric Routing (GDCR): A Vendor-Agnostic Metadata-Driven Semantic Routing Architecture for Enterprise API Gateways — v6. 0. Zenodo. https: //doi. org/10. 5281/zenodo. 18836272 BibTeX: @articleviana2026gdcr, title = {Gateway Domain-Centric Routing (GDCR): A Vendor-Agnostic Metadata-Driven Semantic Routing Architecture for Enterprise API Gateways — v6. 0, author = Viana, Ricardo Luz Holanda, year = 2026, doi = 10. 5281/zenodo. 18836272, url = https: //doi. org/10. 5281/zenodo. 18836272} Author: Ricardo Luz Holanda VianaEnterprise Integration Architect | SAP BTP Integration Suite ExpertSAP Press e-Bite Author LinkedIn: https: //linkedin. com/in/ricardo-viana-br1984Medium: https: //medium. com/@rhviana

Orchestration Domain-Centric Pattern (ODCP): A Vendor-Agnostic Domain-Semantic Orchestration Topology for Enterprise Integration Platforms - v1.0

Key Points

Abstract

Cite This Study

Also Consider

Also Consider