Please enable JavaScript.
Coggle requires JavaScript to display documents.
EBP Architecture - Coggle Diagram
EBP Architecture
Core Components
Clients
(mobile/ web apps)
Identity
(Authentication)
Edge
(Entry point/ router)
Capabilities
(Business service like payments, accounts, ...)
Custom Integration Services
(Connect to core banking systems)
Storage
Each service has its own database schema
Managed using Liquibase
Default DB: MySQL
Cloud DB: MSSQL Server
Optional storage
AWS S3
Azure Blob Storage
Elasticsearch
Backend Services & API Types
Client APIs
(Public for frontend apps via Edge)
Service APIs
(For internal service-to-service communication)
Integration APIs
(for systems outside Backbase, secured via mTLS)
Internal Service Communication
Services communicate via:
HTTP
(OAuth2 service-to-service)
Async messaging
(message broker likes ActiveMQ, RabbitMQ, ...)
Default broker: ActiveMQ
Cloud option: Azure Service Bus
Service SDK
Most services use Service SDK
(Spring Boot libraries)
Handles:
Authentication between services
Event-drive messaging
Database management
Developers focus mainly on business logic
External Communication
External systems accessed via Integration Services layer
Communication methods:
HTTP (OAuth2)
Event-based messaging
Incoming external request are secured with mTLS
Request Flow
User request flow
App authenticates with identity -> gets external JWT
Request goes through Edge
Edge convert external JWT -> internal token
Forwards request to backend services
External token
never reaches backend services directly
Service Discovery
Edge syncs with service registry to find available services
Uses
Eureka (local / small setups)
Kubernetes API server (production)