Event bus for the bank: nervous system of operations
Transactions, payments, applications, alerts — events flowing across 30-50 systems. Event bus makes them first-class objects.
Discuss Your ChallengeWhy the bank needs an event-driven core
Banking operations — cascade of events: transaction → fraud check → AML check → posting → notification → reconciliation → reporting. Without an event bus every connection is a point-to-point integration.
At 5-year scale a bank has 100+ integrations. Maintenance cost grows faster than operational efficiency.
Event bus turns events into first-class objects: producer publishes, any number of consumers subscribe.
Structural elements
Topics. payments.transfer.completed, loan.application.received, card.transaction.authorized, aml.alert.raised, fraud.case.opened.
Schema registry. Contracts for each event type, versioning.
Producer guarantees. At-least-once, idempotent IDs, ordering within partition.
Consumer patterns. Each consumer holds offset, can re-process.
Dead letter queue for unprocessable.
Observability — throughput, lag, error rates per topic.
Banking-specific concerns
Sensitivity. Payment events contain PII — encryption mandatory, strict access control.
Ordering. Transaction posting must be strictly ordered per account.
Auditability. Every event traced for regulator audit.
Latency. Real-time fraud detection requires events <100ms from source.
Reconciliation. Events vs ledger — discrepancies must be detectable.
Where it usually breaks
Bus exists but no contracts — schema changes break consumers.
Topic naming chaos — every team invents.
Owner absent — schema changes without coordination.
PII in clear text — security incident waiting.
Critical flow with too-loose semantics — payment posted twice via retry.
Governance
Every topic has an owner.
Schema changes — PR review with consumer acknowledgement.
PII — encrypted, access controlled.
Operating routine — weekly top consumers/producers, lag review.
Related
- /en/architecture/banking-around-core-architecture/ — wrap core
- /en/architecture/banking-cdp-architecture/ — CDP consumer
- /en/architecture/banking-realtime-decisioning/ — decisioning consumer
- /en/insights/banking-integration-debt/ — integration debt
What else is worth exploring
Topics from the same area we usually explore together
CRM
Not an off-the-shelf CRM, but a properly built customer management contour — from first contact to loyalty.
→SolutionBI
Analytics is not pretty charts on the wall. It's the answer to 'why?' before the problem becomes a loss.
→SolutionContact Center
The contact center is not a phone station — it's the point where a client decides: stay with you or leave. The question is how it's built…
→SolutionOnboarding
Onboarding is your company's first impression. If it takes 5 days and 12 paper forms, there won't be a second impression.
→I do not just write about this. I can come in, examine your situation and design a solution for your specific landscape.
Discuss applying this →Ready to discuss your challenge?
Tell me what's not working or what needs to be built. First conversation — no obligations.
Usually respond within a few hours