The latest articles on DEV Community by Ricardo Viana (@rhviana). https://dev.to/rhviana https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3770340%2F77d210ec-8213-4b79-8dd2-74cb2c38f36e.jpg https://dev.to/rhviana en Ricardo Viana Tue, 03 Mar 2026 08:17:32 +0000 https://dev.to/rhviana/gateway-domain-centric-routing-gdcr-the-foundation-version-v60-l56 https://dev.to/rhviana/gateway-domain-centric-routing-gdcr-the-foundation-version-v60-l56 <p>Building Metadata-Driven Domain-Centric Routing for API Gateways</p> <p>Modern API integration landscapes often end up fragmented:</p> <p>proxy-per-backend systems</p> <p>exploding configuration artifacts</p> <p>frequent redeploys for every service change</p> <p>tight coupling between routing logic and vendor platforms</p> <p>What if instead of continuously rebuilding proxy layers, we treat routing as a governance layer orchestrated by metadata and domain semantics?</p> <p>In a recent independent research effort, I explored an architectural model called Gateway Domain-Centric Routing (GDCR) — a vendor-neutral, metadata-driven approach that separates:</p> <p>✅ Immutable execution plane (proxies + routing engine)<br> ✅ Mutable control plane (metadata + routing definitions)</p> <p>The core idea is that when new backends or vendors are introduced, the system doesn’t require modifying the routing proxies or redeployment. Instead, the routing engine reads updated metadata and resolves requests according to business domain semantics.</p> <p>This model was validated across multiple platforms (Kong, SAP BTP, AWS, Azure) using SAP CPI as backend. Over 1,499,869 requests were processed with:</p> <p>✔ 99.9916% end-to-end success<br> ✔ 100% routing resolution success (zero routing failures)</p> <p>The full paper defines the routing lifecycle, action normalization, metadata strategy, and design principles.</p> <p>If you’re interested in domain-centric API governance, metadata-driven routing, or scalable integration patterns, feel free to read the full documentation here:</p> <p>👉 <a href="https://zenodo.org/records/18836272" rel="noopener noreferrer">https://zenodo.org/records/18836272</a></p> <p>I’d be happy to discuss how this pattern can be applied in real enterprise environments.</p> <p>Author: Ricardo Luz Holanda Viana<br> Enterprise Integration Architect | SAP BTP Integration Suite Expert<br> SAP Press e-Bite Author</p> <p>LinkedIn: linkedin.com/in/ricardo-viana-br1984<br> Medium: medium.com/<a class="mentioned-user" href="https://dev.to/rhviana">@rhviana</a></p> apigateway softwareengineering microservices