DEIP v2.0 · 2026

The Domain
Never Lies.

DEIP is a semantic control plane for enterprise integration — a governance model where domain intent is the only valid primary key across every layer of your architecture.

"Technology is transient. The domain never lies."

DEIP Metadata Wizard → Learn the Architecture
DEIP Architecture Overview
DEIP — Semantic Control Plane
⬡ THE DOMAIN LAYER
└── SDIA — Runtime Architecture
├── GDCR — Gateway Layer
├── DDCR — Resolution Engine
├── ODCP — Orchestration Layer
├── DCEP — Event Layer
└── DCBP — Data Layer (WIP)
⬡ THE EXECUTION LAYER
└── SAP · AWS · Azure · GCP · Kong · MuleSoft · Kafka · Salesforce · ServiceNow · Solace · Workday · IoT · AI/LLM · & other vendors
2,067,904
Requests validated with DDCR
100%
Routing resolution
5
Architecture layers
The Problem

Integration chaos is a
naming problem in disguise.

In most enterprise landscapes, integration artifacts are named after the platform that runs them — not the business intent behind them. The result is a fragile, unmaintainable sprawl that breaks the moment a vendor changes or an engineer leaves.

❌ Technology-first naming
iFlow_Salesforce_CreateOrder_PROD
iFlow_SF_Orders_Inbound_v2_FINAL
iFlow_SAP2SF_OrderSync_BACKUP
iFlow_COPY_OrderSync_DONOTDELETE
✅ Domain-first naming (SDIA)
sales.o2c.orders.create.salesforce.v1
/sales/o2c/orders/create
gdcrorderscSalesforceId01:http
sales.o2c.orders.created
🔴
Proxy sprawlOne proxy per backend. Every new vendor triggers a new deployment, a new name, a new config artifact.
🔴
Knowledge locked in namesWhen the developer who named the artifact leaves, nobody knows what it does or which domain it belongs to.
🔴
Platform couplingArtifacts tied to SAP, MuleSoft, or Kafka by name can't survive platform migrations without a full rename.
🟢
DEIP / SDIA approachDomain intent as the only primary key. The platform is an implementation detail. The name encodes the business, not the technology.
Architecture Transformation

From Frankenstein landscape
to domain governance.

Most enterprise integration landscapes grow organically — by project, by vendor, by whoever was on call. DEIP replaces that sprawl with a single primary key: domain intent.

Integration governance model
As-is vs to-be enterprise integration governance As-is Enterprise Integration Architecture Landscape Execution layer — fragmented by platform and project SAP CPI MuleSoft Kafka Azure Int. SAP APIM Kong GW AWS SQS Salesforce CRM ServiceNow ITSM 🧟 Frankenstein landscape Tight coupling · no domain key · platform sprawl Knowledge erosion when engineers leave Business Projects · demands · integration Business Projects · demands · integration To-be Domain-Governed Architecture Domain intent DEIP Decision model · semantic control SDIA Governance · topology · grammar patterns · naming conventions Execution layer SAP · AWS · Azure · Kong · MuleSoft Kafka · Solace · IoT · AI/LLM Intent explicit · domain governed · platform-agnostic Zero platform coupling · knowledge preserved ↺ loop
Swipe horizontally on mobile to inspect the full diagram.
What is DEIP

A semantic control plane
for enterprise integration.

DEIP — Domain Enterprise Integration Pattern — is a vendor-neutral architectural governance model created in 2026. It defines how domain intent flows through every layer of an enterprise integration landscape.

DEIP Decision Pipeline
1
Intent
What does the business need to do?
2
Interaction Type
Sync, Async, Event, Batch, Stream?
3
Quality Profile
Latency, reliability, consistency requirements
4
Integration Capability
Which pattern? GDCR, ODCP, DCEP…
5
Protocol Profile
REST, gRPC, AMQP, MQTT, SOAP, JDBC…
6
Platform Binding
SAP · AWS · Azure · Kong · Kafka · IoT

DEIP does not replace your integration platform. It governs how you think about and name everything that runs on it. The platform is the last decision — not the first.

The model crystallized from two SAP-oriented routing patterns into a five-layer semantic architecture. First documented in 2026 during a late-night architecture review in Warsaw, Poland.

"Everything begins with a single primary key: the intent of the domain. The domain never lies."

The runtime implementation of DEIP is SDIA — Semantic Domain Integration Architecture — a five-layer reference architecture that maps each governance decision to a concrete runtime layer.

DEIP Metadata Wizard →
SDIA — Ecosystem

One domain. Every layer.
Zero platform coupling.

SDIA is the runtime governance layer of DEIP. Each pillar governs a specific layer of the ecosystem — all indexed by domain intent, never by technology.

SDIA architecture layers — click a pillar to explore
SDIA
Semantic Domain Integration Architecture
GDCR DDCR ODCP DCEP DCBP
🌐 GDCR Gateway Domain-Centric Routing Gateway · API Management
Active USPTO™ 99680660
Explore GDCR →
API Gateway SAP BTP APIM Kong AWS API GW Azure APIM MuleSoft
🔑 DDCR Domain Driven-Centric Router Resolution Engine · Routing
Active USPTO™ 99691792
Explore DDCR →
Gateway SAP APIM KVM Redis / DynamoDB IoT AWS IoT · MQTT LLM OpenAI · Claude
🔗 ODCP Orchestration Domain Composition Orchestration · iPaaS
Active USPTO™ 99704128
Explore ODCP →
iPaaS SAP CPI MuleSoft Boomi Azure Integration Snaplogic
⚡ DCEP Domain-Centric Event Pattern Event Layer · Streaming
Active
Explore DCEP →
Event / Broker SAP EM / AEM Solace Kafka RabbitMQ
🗄️ DCBP Domain-Centric Backend Pattern Data Layer · WIP
Coming Soon
Under Development CDC Pipelines Data Products
SDIA Naming Generator →
Interactive Simulations

See the domain
think for itself.

Two hands-on simulators — one to validate your integration decision using DEIP, one to generate domain-governed naming using SDIA. Input your business scenario, get the architecture back.

🧠
Simulation DEIP
Decision Engine · Pattern Resolver

Describe your business integration scenario. DEIP analyses the domain intent, interaction type, and quality profile — then resolves the correct integration pattern and layer binding.

DEIP · Decision Engine · live
› intent: › pattern: › layer: › binding: ━━━━━━━━━━━━━━━━━━━━
⚡ Launch DEIP Simulation → ✦ v2.0 live
🔗
Simulation SDIA
Naming Engine · Convention Generator

Enter your domain, subdomain, entity and action. SDIA generates the complete naming convention across every integration object — iFlow, API route, topic, queue — all domain-governed.

SDIA · Naming Engine · live
› domain: › iFlow: › route: › topic: ━━━━━━━━━━━━━━━━━━━━
⚡ Launch SDIA Simulation → ✦ v1.0 live
Validation Proof of Concept

Tested at scale.
Not just on paper.

GDCR and DDCR validated in Trial Accounts — cross-atlantic Newman execution Poland → US → Poland, across multiple enterprise platforms and programming languages. Stress-tested with over 2M+ requests before first publication.

2,067,904
Total requests with DDCR logic
99.99%
End-to-end success rate
100%
Routing resolution success
0
Routing failures
Site Analytics

Who is exploring DEIP?

Live visitor counter and platform distribution — updated in real time.

👁
—
Total Visits
The Domain never sleeps.
Live counter
Vendor Distribution
Which platforms are architects working with?
Loading…
Professional Distribution
Who is exploring DEIP?
Loading…
Ricardo Luz Holanda Viana
Ricardo Luz Holanda Viana
Enterprise Integration Architect · DDCR™ Inventor · SAP BTP Expert

Warsaw, Poland — Ricardo is an Enterprise Integration Architect specializing in SAP BTP Integration Suite and large-scale iPaaS governance. He created DEIP and SDIA in 2026 after years of observing the same anti-patterns: platform-coupled artifact naming, proxy sprawl, and institutional knowledge that disappears when engineers leave.

GitHub LinkedIn ORCID DOI — DEIP SAP Community DEV.to
🔒

Intellectual Property Notice

Protected under CC BY 4.0 Internacional and USPTO trademarks. Free for use, open source framework.
DOI: 10.5281/zenodo.18877635 · © 2026 Ricardo Luz Holanda Viana

DEIP.SDIA.GDCR.DDCR.ODCP.DCEP
DOMAIN.SUB.ENTITY.ACTION.TARGET.v1
ｱｲｳｴｵｶｷｸｹｺｻｼｽｾｿﾀﾁﾂﾃﾄ
/sales/o2c/orders/create/salesforce
gdcrorderscSalesforceId01:http
010011010110100101101001011010
INTEGRATION.FLOW.ORCHESTRATION
API.GATEWAY.RESOLUTION.ENGINE
ｾﾏﾝﾃｨｯｸｷｰﾊﾟﾀｰﾝ
EVENT.STREAM.BROKER.TOPIC.DLQ
0101101001011010010110100101
NAMESPACE.TAXONOMY.GOVERNANCE
ROUTING.DIRECT.RESOLVE.BACKEND
DOMAIN.INTENT.PRIMARY.KEY
ｾﾏﾝﾃｨｯｸﾅﾐﾝｸﾞ
010101010101010101010101010101
SEMANTIC.CONTROL.PLANE
ZENODO.DOI.10.5281.18877635
WARSAW.POLAND.ARCHITECTURE
PROTECTED.USPTO.TRADEMARK
ｱｲｳｴｵｶｷｸｹｺｻｼｽｾｿﾀﾁﾂﾃﾄﾅﾇﾈﾉﾊﾋﾌﾍﾎﾏﾐﾑﾒﾓﾔﾕﾖﾗﾘﾙﾚﾛﾜﾝ
INTELLECTUAL.PROPERTY.PROTECTED
DEIP.SDIA.GDCR.DDCR.ODCP.DCEP
010011010110100101101001011010
USPTO.99680660.99691792.99704128
CC.BY.4.0.ATTRIBUTION.REQUIRED
ZENODO.DOI.10.5281.18877635
RICARDO.LUZ.HOLANDA.VIANA.2026
ｾﾏﾝﾃｨｯｸｺﾝﾄﾛｰﾙﾌﾟﾚｰﾝ
PROTECTED.UNDER.COPYRIGHT.LAW
UNAUTHORIZED.USE.PROHIBITED
0101101001011010010110100101
DOMAIN.ENTERPRISE.INTEGRATION
SEMANTIC.CONTROL.PLANE
ｾﾏﾝﾃｨｯｸﾅﾐﾝｸﾞｺﾝﾍﾞﾝｼｮﾝ
NAMESPACE.TAXONOMY.STRUCTURE
INTEGRATION.PATTERN.GOVERNANCE
010101010101010101010101010101
WARSAW.POLAND.ARCHITECTURE
DEIPv2.0.SDIA.GATEWAY.ROUTING
🔒
Intellectual Property Notice

DEIP / SDIA

This work is licensed under CC BY 4.0 Internacional
and includes registered USPTO trademarks.

Usage is permitted under attribution —
credit to the original author is required.

The Domain Was Missing

Built solo in 35 days (Feb–Mar 2026), this framework distills 17 years of architecture experience and hands-on enterprise integration delivery across real-world landscapes. The same pattern kept appearing: a fragmented, uncontrolled architecture — what I define as a Frankenstein Landscape, driven by continuous sprawl and proliferation of integration artifacts.

The same problem kept repeating: the DOMAIN was missing. Systems were named by vendor, tool, or platform, while business meaning disappeared from the topology itself.

DEIP organizes the landscape, deciding the DOMAIN Intent before the technology.

SDIA sustains domain intent through end-to-end naming conventions for all integration objects, independently of the technology.

It is an open source framework, open to everyone, and built for reuse.

Choose your
integration platform

Helps map the DEIP community · anonymous · one click

Select your vendor
SAP SAP
AWS AWS
Azure
Google
Kong
MuleSoft
Kafka
Solace
Other
Select your role
👑 CTO / CIO
🏛️ Enterprise Architect
🔌 Ent. Int. Architect
🏗️ Solutions Architect
🔗 Integration Architect
🏆 Principal Architect
💻 Expert Developer
🔍 Curious
🕵️ Anonymous
Select one platform and one role to continue