> ## Documentation Index
> Fetch the complete documentation index at: https://grandcentral.backbase.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Sync Hub
> Real-time event distribution platform for banking data synchronization and multi-system integration
Sync Hub is a managed event distribution platform that enables real-time data synchronization across all your banking systems, going beyond traditional synchronous APIs to support complex integration patterns.
## Why Sync Hub?
Modern banking systems face critical data orchestration challenges that synchronous APIs alone cannot solve:
**The data synchronization problem**
Banking data originates from multiple sources simultaneously - digital channels, branch systems, core banking, and external vendors. Keeping all systems synchronized in real-time while ensuring data consistency, quality, and distribution to multiple consumers is a fundamental challenge in modern financial services.
Sync Hub addresses the following challenges.
**Data orchestration complexity:** Managing data flow between multiple systems with different timing, formats, and requirements creates exponential integration complexity. Each new system connection multiplies the coordination challenges.
**Multi-system distribution:** Distributing the same data event to multiple consuming systems with different needs means building separate integrations for each consumer. This creates maintenance nightmares when event formats change.
**Real-time synchronization:** Keeping all systems updated immediately when data changes in any source system requires complex webhook handling, polling mechanisms, or custom event streaming infrastructure.
**Data quality and consistency:** Ensuring data accuracy, validation, and enrichment across all integration points demands coordinated validation logic, transformation rules, and error handling that's duplicated across every integration.
## How Sync Hub works
Sync Hub operates as a managed event distribution platform where you build connectors that publish and consume events:
Your integration connectors publish events to Sync Hub when data changes occur in source systems.
**Publishing sources:**
* Webhook endpoints receiving vendor notifications
* Event consumers reading from external message brokers
* File processors handling batch uploads
* Database change data capture streams
* Direct API integrations with enrichment
Sync Hub distributes events to multiple consuming systems based on configuration and routing rules.
**Distribution capabilities:**
* Fan-out to multiple consumers simultaneously
* Content-based routing and filtering
* Guaranteed delivery with retry logic
* Order preservation when required
* Dead letter handling for failures
Grand Central manages the underlying event infrastructure so you can focus on business logic.
**Platform handles:**
* Scalable event processing infrastructure
* High availability and disaster recovery
* Performance monitoring and optimization
* Security and compliance controls
* Operational maintenance and updates
## Why managed infrastructure matters
Building and operating event distribution infrastructure is significantly more complex than it appears. Sync Hub eliminates months of engineering work by handling the operational complexity so you can focus on banking logic. The following sections describe what the platform provides.
### What you don't have to build
Sync Hub manages the following so you can focus on banking logic:
* **Event broker operations** - fully managed: high-availability message broker clusters with multi-zone deployment, automatic failover, capacity planning and scaling, version upgrades, and performance tuning. This eliminates 6-12 months of infrastructure engineering and ongoing operational overhead.
* **Security and compliance** - built-in: tenant isolation and data segregation, encryption in transit and at rest, access control and authentication, audit logging, and compliance reporting. See [Platform Security](/platform/security) for comprehensive security architecture including namespace-based tenant isolation.
* **Reliability engineering** - handled: guaranteed message delivery, dead letter queue handling, retry logic with exponential backoff, circuit breakers, fault tolerance, and message ordering guarantees. This eliminates complex distributed systems engineering to ensure no events are lost.
* **Operational resilience** - guaranteed: Tier-based uptime SLA (99.5-99.9% based on your Grand Central service tier) with monitoring, disaster recovery and backup, performance monitoring and alerting, incident response and remediation, and capacity management. See [High Availability and DR](/platform/high-availability) for RTO/RPO commitments and multi-region architecture.
### Banking-specific complexity
Beyond general event streaming infrastructure, banking integrations require specialized capabilities:
* **Multi-pattern support** - banking vendors use diverse integration patterns - webhooks, event streams, batch files, and API enrichment - often simultaneously for a single vendor. Payment processors like Alacriti send real-time webhook notifications, daily settlement files via SFTP, and transaction lifecycle events through Kafka. Sync Hub provides unified handling of all these patterns without requiring separate infrastructure for each.
* **Schema evolution and versioning** - banking systems evolve over time with schema changes, new fields, and deprecated attributes. Sync Hub manages schema versioning and backward compatibility automatically, preventing integration breakage when systems are updated. This eliminates manual schema migration coordination across multiple consuming systems whenever a vendor updates their data format.
* **Compliance and audit requirements** - banking regulations require complete audit trails, data retention policies, and compliance reporting for all data movement. Sync Hub provides built-in compliance capabilities including complete event lineage tracking, retention policy enforcement, audit log generation, and compliance report automation.
* **Consumer lifecycle management** - real-world banking environments have dozens of consuming systems with different scaling requirements, failure modes, and processing speeds. Sync Hub manages per-consumer delivery guarantees, back pressure, and error handling independently, eliminating the need to build custom consumer group management, offset tracking, and per-consumer retry logic for each integration.
### Engineering time investment
Building equivalent event distribution infrastructure requires significant engineering investment:
| Component | DIY Effort | Sync Hub |
| ----------------------------------- | --------------- | -------- |
| **Message broker setup** | 4-6 weeks | Included |
| **High availability configuration** | 3-4 weeks | Included |
| **Security and tenant isolation** | 6-8 weeks | Included |
| **Monitoring and alerting** | 3-4 weeks | Included |
| **Dead letter queue handling** | 2-3 weeks | Included |
| **Schema versioning** | 4-6 weeks | Included |
| **Webhook endpoint management** | 3-4 weeks | Included |
| **File processing framework** | 4-6 weeks | Included |
| **Multi-consumer routing** | 3-4 weeks | Included |
| **Testing and hardening** | 6-8 weeks | Included |
| **Documentation and runbooks** | 2-3 weeks | Included |
| **Ongoing operations** | 1-2 FTE ongoing | Managed |
**Total DIY investment** - 6-12 months initial development + ongoing operational overhead
**With Sync Hub:** focus immediately on banking integration logic
## Sync Hub vs. synchronous APIs
Understanding when to use Sync Hub versus traditional synchronous API integrations:
| Scenario | Synchronous APIs | Sync Hub |
| --------------------------------- | -------------------------- | ------------------------------------ |
| **Request-response patterns** | ✅ Ideal | ❌ Not applicable |
| **Multi-system distribution** | ⚠️ Requires multiple calls | ✅ Single publish, multiple consumers |
| **Real-time event notifications** | ⚠️ Polling required | ✅ Push-based delivery |
| **Vendor webhook integration** | ❌ Complex to handle | ✅ Built for webhooks |
| **Batch file processing** | ⚠️ Manual orchestration | ✅ Automated processing |
| **Asynchronous workflows** | ⚠️ Complex implementation | ✅ Native support |
| **Decoupled systems** | ⚠️ Tight coupling | ✅ Loose coupling |
**Use both together**
Sync Hub and synchronous APIs complement each other. Use synchronous APIs for request-response patterns and Sync Hub for event distribution, multi-system updates, and asynchronous workflows.
## Sync Hub vs. DIY event streaming
Many teams consider building custom event infrastructure using message brokers like Kafka or RabbitMQ. Understanding the true scope of this undertaking is critical for making informed architecture decisions.
The following comparison illustrates the complexity of building your own event streaming infrastructure.
### What DIY event streaming actually requires
Building your own event streaming infrastructure typically involves:
* **Core infrastructure demands 20+ components** - message broker cluster (Kafka/RabbitMQ), Zookeeper, load balancers, storage with backup. Producer and consumer frameworks, schema registry, dead letter queues, retry logic. Monitoring, log aggregation, metrics dashboards, distributed tracing, incident management. Authentication, authorization, encryption, tenant isolation, audit logging, compliance reporting. Infrastructure as Code, CI/CD pipelines, auto-scaling, disaster recovery, multi-region deployment.
* **Security and operations aren't optional** - every component needs hardening. Every failure mode needs handling. Every metric needs monitoring. Every incident needs response procedures.
* **Banking-specific requirements multiply the complexity** - webhook management means secure endpoints, signature validation, rate limiting, DDoS protection. File processing means SFTP servers, format parsers (CSV, XML, fixed-width), batch orchestration, error handling, large file streaming. Event enrichment means cache layers, API integration frameworks, performance optimization. Multi-consumer patterns mean per-consumer guarantees, offset tracking, back pressure handling, consumer-specific transformations. Compliance means event lineage, retention policies, regulatory reports, audit trails, data residency.
* **Daily operations grind never stops** - monitor health, respond to alerts, investigate lag, manage dead letters, review audit logs. Then weekly: capacity planning, performance tuning, security patches, backup verification, documentation updates. Monthly: version upgrades, disaster recovery drills, compliance reports, cost optimization, technical debt.
* **Staffing is the hidden killer** - 1-2 FTE for operations, on-call rotation for 24/7 support, subject matter experts for escalations, dedicated security review, ongoing vendor coordination. You need distributed systems expertise, message broker administration, Kubernetes operations, banking domain knowledge, security and compliance understanding.
* **Hidden costs add up fast** - 6-12 months initial development. Ongoing feature work, bug fixes, documentation, training. 24/7 operations team, incident response, performance tuning, security management, compliance audits. Engineering time not spent on banking features. Delayed integrations. Slower vendor responses. Limited capacity for new use cases. Technical debt accumulation. Event loss risks. Security vulnerabilities. Compliance violations and fines. System outages. Integration failures affecting customers.
### Sync Hub approach
Instead of building and maintaining this complex infrastructure, Sync Hub provides:
**Included out-of-the-box:**
* Managed event infrastructure with tier-based SLA (99.5-99.9%)
* Banking-specific integration patterns (webhooks, files, streams, enrichment)
* Multi-consumer distribution with guaranteed delivery
* Complete security, compliance, and audit capabilities
* Operational monitoring, alerting, and support
* Disaster recovery and high availability
* Continuous updates and improvements
**You focus on:**
* Banking business logic and rules
* Vendor-specific data transformation
* Consumer application requirements
* Customer experience
**Result:** Weeks to production instead of months, with enterprise-grade reliability and ongoing operational support included.
## Core capabilities
Support for webhooks, event streaming, file processing, enrichment, and multi-consumer distribution
Customer synchronization, payment processing, transaction distribution, and more
Scalable, highly available event processing with monitoring, security, and disaster recovery
## Key benefits
Sync Hub delivers the following benefits:
* **Real-time synchronization** - immediate data consistency across all systems with event-driven architecture and push-based delivery. No more polling or batch synchronization delays.
* **Reduced integration complexity** - single publish point with automatic distribution to multiple consumers eliminates point-to-point integrations. Add new consumers without modifying producers.
* **Scalable architecture** - handle high-volume event processing with auto-scaling and distributed processing capabilities. From hundreds to millions of events per day without infrastructure changes.
* **Decoupled systems** - loose coupling between producers and consumers enables independent system evolution and maintenance. Upgrade one system without affecting others.
* **Operational resilience** - built-in retry logic, dead letter handling, and guaranteed delivery ensure reliable event processing. No events lost due to transient failures.
* **Managed infrastructure** - focus on business logic while Grand Central handles infrastructure, scaling, monitoring, and operations. No message broker expertise required.
## Platform inclusion
Sync Hub is included with both Grand Central offerings, providing managed event distribution for your integrations at no additional per-message cost. The following sections describe what's included and how to choose your implementation.
### What's included
Sync Hub includes the following:
* **Core platform capabilities** - always included: managed event infrastructure with tier-based SLA (99.5-99.9% based on your Grand Central service tier), all integration patterns (webhooks, streams, files, enrichment), multi-consumer distribution, guaranteed message delivery, dead letter queue handling, security and compliance features, monitoring and alerting, and disaster recovery with high availability.
* **No hidden costs** - Sync Hub is included with the Grand Central platform. No per-message charges, no per-consumer fees, no egress charges for event distribution. Operational support, platform updates, and improvements are all included.
### Choosing your implementation
Sync Hub comes pre-configured with our productized connectors for common banking integrations.
**What you get:**
* Pre-built integration patterns for major vendors
* Standard event schemas and transformations
* Automated monitoring and alerting
* Out-of-the-box webhook handling
* Managed file processing
* Pre-tested and hardened configurations
**Ideal for:**
* Standard payment processing integrations (Alacriti, Volante, Oracle FLEXCUBE)
* Common core banking synchronization
* Established vendor relationships with standard APIs
* Faster time-to-production requirements
**When to choose this:**
Your integration requirements match our pre-built connectors and you want the fastest path to production with the least custom development.
Build custom integrations using Sync Hub with full control over your event processing logic.
**What you get:**
* Full access to Sync Hub infrastructure and patterns
* Connector framework for building producers and consumers
* Configurable event routing and filtering
* Custom data transformation logic (JavaScript, Python, or Java)
* Tailored monitoring dashboards
* Complete flexibility for unique requirements
**Ideal for:**
* Unique integration requirements not covered by productized connectors
* Custom vendor integrations with proprietary protocols
* Specialized business workflows and orchestration
* Legacy system modernization with complex mapping
* Internal system integrations (CRM, core banking, analytics)
**When to choose this:**
Your integration requirements are unique, you're integrating with custom or internal systems, or you need specialized data transformation logic that productized connectors don't provide.
**Usage limits and scaling**
Sync Hub scales automatically to handle your event volume. For extremely high-volume scenarios (millions of events per day), consult with the Grand Central team to ensure optimal configuration and capacity planning.
## Learn more
[**Integration patterns**](/platform/sync-hub-integration-patterns) - Explore the five core integration patterns and when to use each one.
[**Use cases**](/platform/sync-hub-use-cases) - See real-world examples of Sync Hub in action across banking scenarios.
[**Platform overview**](/platform/overview) - Return to the complete Grand Central platform overview.