Ready to Start?Discover our quick start guide and build your first application in 5-10 minutes
Quick Start Guide
Download IgniteARCHITECTURAL BACKBONE
CORE FEATURES
DATA PLACEMENT & PROCESSING
OPERATIONAL EXCELLENCE
ADDITIONAL USE CASES
Download IgniteARCHITECTURAL BACKBONE
CORE FEATURES
DATA PLACEMENT & PROCESSING
OPERATIONAL EXCELLENCE
ADDITIONAL USE CASES
Digital Integration Hub
With Apache Ignite
Unified data access layer that aggregates multiple back-end systems
Digital Integration Hub Pattern
A digital integration hub (DIH) is an architectural pattern that aggregates multiple back-end systems and databases into a low-latency shared data store. Applications access unified data through a single interface rather than querying multiple disparate systems.
This pattern applies to both Ignite 2 and Ignite 3. Ignite functions as the centralized data layer that synchronizes with back-end systems through streaming, CDC, or event-based integration. System consolidation reduces infrastructure complexity and operational overhead.
System Consolidation Benefits
Ignite consolidates access to multiple back-end systems through a unified data layer
Unified Data Access
Single interface aggregates data from multiple back-end databases and systems. Applications query one store instead of managing connections to multiple systems. Reduces application complexity by eliminating logic for accessing numerous data sources. Standard SQL or key-value APIs for data access across consolidated systems.
Infrastructure Consolidation
Replace multiple per-application databases with shared data layer. Significant infrastructure cost reduction through system consolidation. Operational overhead reduced by centralizing data management. Memory-first architecture delivers low-latency access to aggregated data.
Architecture Pattern
Data Aggregation From Multiple Systems
Ignite serves as centralized data layer that aggregates data from multiple back-end systems through synchronization mechanisms.
Integration Pattern: Back-end systems synchronize data to Ignite through streaming platforms, change data capture tools, or event-based integration. Applications query Ignite instead of accessing back-end systems directly. Ignite maintains aggregated view of data across multiple sources.
Synchronization Options: Ignite 2 provides CacheStore interface for write-through and write-behind synchronization. Ignite 3 supports similar patterns through custom integration layers. Both versions work with streaming platform connectors for bi-directional synchronization.
Performance Characteristics: Memory-first architecture delivers low-latency queries across aggregated data. Eliminates network hops to multiple back-end systems. Horizontal scalability handles growing data volumes from multiple sources.
When This Pattern Works
This architecture pattern is best for:
- Applications requiring unified access to data scattered across multiple back-end systems
- Omnichannel platforms aggregating customer data from disparate sources
- API gateways serving data from multiple legacy systems
- Real-time dashboards requiring low-latency access to aggregated data
Example Use Cases:
- Customer 360: Aggregate customer data from CRM, billing, support, and marketing systems into unified view accessible through single interface
- Omnichannel Retail: Consolidate inventory, pricing, and customer data from multiple back-end systems for consistent experience across channels
- API Offloading: Reduce load on back-end systems by serving API requests from Ignite with data synchronized from multiple sources
Key Benefits
Reduced Application Complexity
Applications query single unified interface instead of managing connections to multiple back-end systems. Eliminates logic for accessing numerous data sources. Reduces network connections and authentication overhead. Standard SQL or key-value APIs simplify data access patterns.
Infrastructure Cost Reduction
System consolidation replaces multiple per-application databases with shared data layer. Significant cost reduction through centralized data management. Operational overhead reduced by eliminating multiple database instances. Memory-first architecture delivers low-latency access without specialized hardware.
Low-Latency Data Access
Memory-first storage delivers low-latency queries across aggregated data. Eliminates network hops to multiple back-end systems. Single query returns data from multiple sources. Reduces response times for applications accessing consolidated data.
Both Versions Supported
This pattern works with both Ignite 2 and Ignite 3. Ignite 2 provides CacheStore interface for synchronization. Ignite 3 supports custom integration layers with streaming platforms. Both versions deliver same consolidation benefits.
Synchronization Mechanisms
Ignite 2 Synchronization
CacheStore interface enables write-through and write-behind synchronization with back-end systems. Ignite 2 automatically writes changes to external databases. Transaction coordination across Ignite cluster and external transactional databases. Supports uni-directional synchronization from back-end systems to Ignite.
Bi-Directional Synchronization
Both versions work with streaming platforms for bi-directional synchronization. Change data capture tools stream database changes to Ignite. Event-based integration through message queues. Custom integration layers for specific back-end systems.
Important Considerations
Synchronization Complexity
Maintaining data consistency across multiple back-end systems requires careful synchronization design. Eventual consistency windows may exist during synchronization delays. Conflict resolution strategies needed for bi-directional synchronization. Monitoring required to detect synchronization failures.
Data Governance
Aggregating data from multiple systems requires clear data governance policies. Access control and security must be maintained across consolidated data. Compliance requirements (GDPR, CCPA) apply to aggregated data. Data lineage tracking needed for auditing purposes.
Ready to Start?
Explore More Use CasesLearn about other Ignite use cases
Use Cases Overview