Semantic Domain Integration Architecture (SDIA): A Vendor‑Agnostic Semantic Governance Model for Enterprise Integration — v1.0

⚠️ Deprecated Notice Semantic Domain Integration Architecture (SDIA) — Version 1.0 is now superseded by Version 2.0. This record is retained for historical reference only. All new implementations, references, and citations SHOULD use SDIA v2.0 as the authoritative specification.

Simple orientation

In the simplest possible way, SDIA means that the whole integration landscape of a company should follow the meaning of the business, not the confusion of technology.

If someone asks for something related to sales, finance, logistics, or healthcare, that meaning should stay the same from the beginning to the end. It should not disappear just because the request passes through gateways, routers, orchestration tools, packages, credentials, or backend systems.

A simple abstract example is a hospital. A person arrives asking for emergency, cardiology, or pediatrics. That meaning should guide the whole journey. The reception should understand it, the internal direction should preserve it, and the right department should execute it. The patient should not be forced to understand corridors, storage rooms, internal codes, or staff-only structures. The hospital may be technically complex inside, but the experience must remain organized by purpose.

Another example is an airport. A traveler follows meanings like check-in, security, boarding, or baggage claim. Even if many internal systems, teams, and operations exist behind the scenes, the journey still makes sense because the structure is organized around what the traveler is trying to do. The internal complexity exists, but it does not break the meaning of the journey.

That is the idea of SDIA. It says that integration should work the same way. The business meaning enters clearly, moves through the architecture without being lost, and reaches execution still carrying the same semantic identity.

So in simple terms, SDIA is the full architecture that keeps business meaning alive across the entire integration flow. It starts at the semantic entry point, continues through runtime resolution, and ends in orchestration and execution. The domain is the stable language. Technology stays in the background.

Professional

Semantic Domain Integration Architecture (SDIA) is an enterprise integration architecture that organizes the full integration landscape around business domain semantics rather than technology, vendor, or platform structure. Its core principle is that the business meaning of an interaction becomes the primary reference across every integration layer, from entry point to runtime resolution to orchestration and backend execution.

Instead of treating integration as a fragmented collection of endpoints, platform artifacts, and vendor-specific configurations, SDIA defines integration as a continuous semantic flow driven by business intent. The same domain language used at the point of request is preserved throughout the architectural chain, ensuring that meaning is not lost when moving across gateways, routing logic, orchestration artifacts, credentials, or execution environments.

SDIA is composed of three independently validated and DOI-published pillars. GDCR defines the semantic gateway façade and establishes the business-readable entry point. DDCR performs deterministic runtime resolution, translating domain meaning into the correct technical destination without relying on static URL logic. ODCP extends the same domain principle into the orchestration layer, ensuring that packages, iFlows, technical users, credentials, and related execution artifacts remain semantically aligned.

Together, these three pillars form a single end-to-end semantic chain. A human-readable business request enters through a semantic gateway, is resolved deterministically at runtime, and is executed through domain-centric orchestration without losing its original meaning. In this model, the business domain becomes the stable organizing layer of integration, while technologies, vendors, and platforms remain replaceable infrastructure.

By making domain semantics the permanent integration language, SDIA reduces the structural fragmentation typically caused by technology-centric integration models. This includes the reduction of proxy sprawl, package sprawl, and credential sprawl across the enterprise stack. In published validation results, SDIA demonstrated 90 percent structural reduction in proxies and packages, 69 percent reduction in credentials, 100 percent routing accuracy across 1,499,869 requests, and validation across four enterprise platforms and four programming languages.

Resume professional

SDIA is a vendor-agnostic, metadata-driven enterprise integration architecture that preserves business domain meaning across the full integration lifecycle, from semantic entry to deterministic routing to domain-centric orchestration and backend execution. By combining GDCR, DDCR, and ODCP, it transforms business intent into the stable execution language of integration, reducing structural sprawl and making the architecture governable, scalable, and technology-independent.

Companion Architectures:

• Gateway Domain-Centric Routing (GDCR) — DOI: https://doi.org/10.5281/zenodo.18582492
• Domain Driven Centric Router (DDCR) — DOI: https://doi.org/10.5281/zenodo.18864832
• Orchestration Domain-Centric Pattern (ODCP) — DOI: https://doi.org/10.5281/zenodo.18876593

Keywords: Semantic Domain Integration, Enterprise Integration Architecture, Domain-Centric Governance, Business Intent Routing, Semantic Chain, Proxy Sprawl, Package Sprawl, Credential Sprawl, Vendor-Agnostic Architecture, Metadata-Driven Governance, GDCR, DDCR, ODCP, SDIA, End-to-End Traceability

License: Creative Commons Attribution 4.0 International (CC BY 4.0)

USPTO Trademark Application: 99680660 — GDCR, DDCR, ODCP

ORCID: https://orcid.org/0009-0009-9549-5862

Citation — APA: Viana, R. L. H. (2026). Semantic Domain Integration Architecture (SDIA): When Business Intent Becomes the Integration Language — v1.0. Zenodo. https://doi.org/10.5281/zenodo.18877636

Citation — BibTeX:

@article{viana2026sdia,
  title  = {Semantic Domain Integration Architecture (SDIA):
            When Business Intent Becomes the Integration Language},
  author = {Viana, Ricardo Luz Holanda},
  year   = {2026},
  doi    = {[SDIA DOI]},
  url    = {https://doi.org/10.5281/zenodo.18877636}
}

Author: Ricardo Luz Holanda Viana

Enterprise Integration Architect 

SAP BTP Integration Suite Expert 

SAP Press e-Bite Author

LinkedIn: https://linkedin.com/in/ricardo-viana-br1984

Medium: https://medium.com/@rhviana

Email: rhviana@gmail.com