Gateway Domain-Centric Routing (GDCR) : A Vendor-Agnostic Metadata-Driven Architecture for Enterprise API Governance - The Foundation - Version v6.0 Deprecated

Simple orientation

In the simplest possible way, GDCR means that a company should be easy to understand from the outside, even if it is complex on the inside. People should reach what they need by meaning, not by hidden structure.

Think about a hospital. A patient should be able to go to cardiology, emergency, or pediatrics without needing to know the building code, the internal corridor map, the storage room logic, or which team manages each floor. The hospital may be very complex inside, but the outside must stay clear and organized by purpose.

Now think about an airport. A traveler should be able to follow signs like departures, arrivals, security, or baggage claim. The traveler does not need to know the wiring, the staff-only routes, the control systems, or the operational layout behind the scenes. What matters is that the airport presents a clear and meaningful structure to the outside world.

A third way to see it is through a university. A student should be able to find admissions, library, finance, or student services by what those things mean, not by knowing which office was moved, which hallway was renamed, or which internal process changed last month.

That is the idea of GDCR. The outside should be organized by clear domains of meaning, while the inside can remain complex, distributed, and controlled.

Professional

Gateway Domain-Centric Routing (GDCR) is the foundational architectural model that organizes enterprise access around business domains rather than technical infrastructure. Its role is to create a stable semantic structure through which APIs, services, and integrations are exposed, governed, and understood. Instead of forcing consumers to depend on gateway-specific paths, proxy designs, backend locations, or vendor logic, GDCR presents enterprise capabilities through domain meaning.

This makes the enterprise easier to govern, easier to scale, and easier to evolve. Internal systems may change, platforms may differ, and routing implementations may vary, but the external structure remains stable because it is anchored in domain semantics rather than infrastructure details.

Composition of GDCR

GDCR is not just a naming idea. It is composed of a small set of architectural elements that work together.

The first component is the domain structure. This defines the major business areas through which enterprise capabilities are organized, such as finance, sales, logistics, healthcare, or education.

The second component is the semantic façade. This is the clear external entry point that represents a domain capability in a stable and meaningful way.

The third component is the governance and identity layer. This gives each capability a controlled identity, clear ownership, and consistent policy boundaries.

The fourth component is the metadata model. This describes how domain meaning, identity, policy, and relationships are represented in a portable and deterministic form.

The fifth component is DDCR. This is the runtime resolution component inside GDCR. In simple terms, GDCR defines the organized domain-based structure, and DDCR is the component that resolves that structure operationally at runtime. So DDCR is not separate from the idea in practice. It is part of the composition that makes GDCR executable.

Integrated version

Gateway Domain-Centric Routing (GDCR) is the foundational architectural model that organizes enterprise access around business meaning instead of technical structure. In the simplest sense, it means the outside of the organization should be clear, stable, and domain-based, even if the inside is complex. Like a hospital, an airport, or a university, people should reach what they need by purpose, not by hidden internal layout. GDCR is composed of domain structure, semantic façades, governance and identity boundaries, metadata, and DDCR as the runtime resolution component that makes the model operational.

Links

• Repository: https://github.com/rhviana/gdcr 

• Figshare v6.0 : https://doi.org/10.6084/m9.figshare.31331683

Citation (superseded by v6.0)

APA:

Viana, R. L. H. (2026). Gateway Domain-Centric Routing - The Foundation - Version 6.0. Zenodo. https://doi.org/10.5281/zenodo.18836272

BibTeX:

@article{viana2026gdcr,
  title   = {Gateway Domain-Centric Routing: A Vendor-Agnostic Metadata-Driven Architecture
             for Enterprise API Governance — v6.0 Edition},
  author  = {Viana, Ricardo Luz Holanda},
  year    = {2026},
  doi     = {10.5281/zenodo.18836272},
  url     = {https://doi.org/10.5281/zenodo.18836272}
}

@misc{viana2026gdcr_assets,
  title        = {Gateway Domain-Centric Routing (GDCR): Companion Repository — v6.0},
  author       = {Viana, Ricardo Luz Holanda},
  year         = {2026},
  howpublished = {GitHub},
  url          = {https://github.com/rhviana/gdcr}
}