Platform value proposition
Boost productivity
Pre-built connectors, transformations, and workflows accelerate development
Low-code and pro-code
Camel DSL for rapid development plus composable pro-code components
Enterprise governance
Built-in scalability, security, monitoring, and integration management
Composable architecture
Library of reusable functional and technical components
Development methodology
The platform follows a “plug and play” development approach through four sequential phases: (1) Start with Templates - begin development using pre-built project templates and scaffolding, (2) Adopt Spec - implement OpenAPI specifications for contract-first development, (3) Reuse Kamelets - compose integrations from reusable functional components, (4) Data Mapping - apply transformations using XSLT or JOLT templates to complete the integration workflow.Technology stack
The platform builds on the following technology layers:- Core technologies - comprise the runtime platform and infrastructure foundation. Runtime platform uses Java as the primary development language, Quarkus as the cloud-native Java framework, Apache Camel as the integration framework, and Camel K/K Native for Kubernetes-native execution. Infrastructure layer provides Kubernetes for container orchestration, Docker for containerization, Helm for package management, and Terraform for infrastructure as code.
- Cloud infrastructure - uses Microsoft Azure for enterprise-grade cloud infrastructure, providing scalability, security, and global availability. Compute services include AKS and Container Instances for workload execution. Networking capabilities span VNet, Load Balancer, and VPN for connectivity. Storage and data services use Azure Storage and Service Bus for persistence and messaging.
- Open source foundation - delivers innovation benefits through collaboration and faster capability development, avoids vendor lock-in through open standards, and provides access to a broad developer talent pool with community contribution and expertise. Components include Grand Central Kamelets (custom integration components for banking use cases), 300+ OSS Components (extensive library of open source integration patterns), GC SDK (development toolkit with templates and utilities), and Enterprise Patterns (proven integration patterns and best practices).
Integration platform components
Understanding the anatomy of a Grand Central integration:BOM (bill of materials)
BOM (bill of materials)
Definition - POM project containing all underlying base-platform dependencies.Purpose - provides consistent dependency management for GC Connectors.Includes - the BOM contains:
- Core platform dependencies
- Developer enablement tooling
- Version alignment
- Conflict resolution
- Simplified dependency management
- Consistent platform versions
- Reduced configuration complexity
Kamelets and SDKs
Kamelets and SDKs
Definition - fundamental units of abstraction for common operations.Purpose - building blocks for Integration Connectors.Types - kamelet types include:
- Source Kamelets: Data ingestion from external systems
- Sink Kamelets: Data output to target systems
- Action Kamelets: Data transformation and processing
- Database connectors (JDBC, MongoDB, etc.)
- Messaging systems (Kafka, RabbitMQ, etc.)
- File processors (FTP, SFTP, S3, etc.)
- Protocol handlers (HTTP, SOAP, etc.)
OpenAPI specification
OpenAPI specification
Definition - project containing OpenAPI/Swagger definitions.Purpose - API contract definition and sharing.Features - features include:
- Standardized API documentation
- Code generation capabilities
- Contract-first development
- JAR packaging for reuse
- Consistent API design
- Automated client generation
- Documentation synchronization
Template-based transformations
Template-based transformations
Definition - configuration supporting data transformation.Supported formats - supported formats include:
- XSLT: XML transformations
- JOLT: JSON transformations
- Data structure mapping
- Field transformations
- Format conversions
- Business rule application
- System data model mapping
- Protocol format conversion
- Business logic implementation
Camel DSL
Camel DSL
Definition - low-code domain specific language for integration patterns.Execution options - options include:
- Local development environment
- Remote platform execution (Camel-K)
- Visual flow design
- Declarative configuration
- Enterprise Integration Patterns
- Hot deployment capabilities
- Reduced code complexity
- Faster development cycles
- Standard pattern library
Developer and operational experience
Developer experience provides real-time development with immediate feedback and testing during the development process.Lean incremental builds
Fast build cycles with incremental compilation and hot reloading
Image reuse
Container image optimization and reuse for faster deployments
Dependency management
Automated dependency resolution and conflict management
Ide integration
Rich IDE support with debugging, testing, and deployment tools
Auto-scaling
Automatic scaling based on load and performance metrics
Monitoring
Comprehensive monitoring and alerting for all integrations
Observability
Full observability with metrics, logs, and distributed tracing
Security
Enterprise security with encryption, authentication, and authorization
Resource optimization
Efficient resource usage with optimization and rightsizing
Traits configuration
Platform traits for behavior customization and optimization
Platform benefits summary
Fast time-to-market
Simplified integrations through API orchestration and data mapping enable rapid business solution delivery
Operational excellence
Fully managed cloud-native platform handling scaling, monitoring, observability, and security
Increased productivity
Low-code design reduces dependency on specialized integration developers