Gateway Domain-Centric Routing (GDCR): A Vendor-Agnostic Metadata-Driven Architecture for Enterprise API Governance - v8.0 - FINAL

GDCR — Gateway Domain-Centric Routing

Layer 1 of the SDIA Ecosystem

This project is not abandoned. It is frozen.

Reason for freeze: The work entered an infinite refinement loop. The architecture evolved, but external peer review, validation feedback, or community contribution did not materialize. Continuing alone without structural feedback ceased to be research and became exhaustion.

GDCR is a vendor-neutral governance model for enterprise API gateways. It replaces technology‑indexed proxy sprawl with a domain‑indexed semantic facade.

Core invariant: one proxy per domain. The consumer sees stable semantic URLs (/sales/orders/create/salesforce). Backend variability is externalized to a metadata control plane (KVM, Redis, DynamoDB). The proxy remains immutable.

Immutability is achieved by separation:

• GDCR = facade contract

• DDCR = deterministic runtime resolution layer (policy, script, filter, or plugin)

• Metadata = mutable control plane

• Proxy = stable data plane

Validated across:

• SAP API Management (JavaScript)

• Kong Gateway (Lua)

• AWS API Gateway (Python)

• Azure API Management (C#)

• Netflix Zuul (Java)

~1.6M requests · zero routing failures.

What GDCR is not: a gateway product or vendor feature. It is an architectural invariant: the domain as the primary key of the API facade.

Links:

• Repository: github.com/rhviana/deip

• DEIP Ecosystem DOI: 10.5281/zenodo.19004802

• Reference implementation (JavaScript): dcrp-js-phantomv12.js

Author: Ricardo Luz Holanda Viana · ORCID: 0009-0009-9549-5862

Citation: Viana, R. L. H. (2026). Gateway Domain-Centric Routing (GDCR) — Version 8.0. Zenodo. https://doi.org/10.5281/zenodo.18582492