How does a typical Core banking Solution architecture looks like ?

Summary

This session provides a clear overview of a typical core banking architecture, divided into four key zones: channel layers, application layer, database, and reporting servers. It explains how front-end channels like mobile apps, internet banking, and ATMs interact with the core banking system via an Enterprise Service Bus, integrating with application servers and databases. The video also covers document management, monitoring through Prometheus, messaging via Swift and Kafka, and reporting using data warehouses or analytical tools. Additionally, it touches on cloud integrations, such as connecting SaaS applications to in-house systems, giving a concise yet comprehensive view of a modern banking solution landscape.

Takeaways

• 🏦 Core banking architecture can be divided into four main zones: channel layer, application layer, database layer, and reporting layer.
• 📱 The channel layer includes user-facing systems like mobile banking, internet banking, call centers, and ATM switches.
• 🔗 All channels typically connect through an Enterprise Service Bus (ESB), enabling integration between systems.
• 🌐 Users access core banking applications via HTTP, interacting through REST APIs (JSON) or SOAP (XML).
• 💻 The application layer hosts different servers such as core banking app servers, integration servers, and ATM processing servers.
• 🏧 ATM switches send ISO 8583 messages, which are processed by specialized ATM application servers.
• 🗄️ The database layer stores all core banking data, with business logic split between application and database layers depending on the system design.
• 📂 Document management systems are used to store supporting documents like customer records and loan application files outside the main database.
• 📊 Monitoring tools like Prometheus collect system metrics and feed them into visualization tools such as Grafana for reporting.
• 💬 Messaging systems like Kafka handle event streaming for notifications such as SMS and WhatsApp alerts.
• 🌍 External integrations like SWIFT use middleware (e.g., IBM MQ) to send financial messages (MT/MX formats).
• 📈 The reporting layer uses a replicated database (via tools like Active Data Guard or GoldenGate) to generate reports without impacting live systems.
• 📉 Reporting tools and data warehouses aggregate and analyze data for enterprise-wide insights.
• ☁️ Cloud-based SaaS applications (e.g., CRM systems) require integration platforms (iPaaS) to connect with on-premise core banking systems.
• 🔄 The overall architecture is complex but modular, enabling scalability, integration, and real-time processing across banking operations.

Q & A

What are the four main zones of a typical core banking architecture?

The four main zones are: 1) Channel Layer, 2) Application Layer, 3) Database Layer, and 4) Reporting Layer.

What components are included in the channel layer?

The channel layer includes mobile banking apps, internet banking, call center interfaces, and ATM switches that connect to the core banking system.

How does the Enterprise Service Bus (ESB) facilitate communication in core banking?

The ESB acts as a central integration hub, connecting various channels to application servers, allowing communication via REST/JSON, SOAP/XML, or ISO 8583 messages from ATMs.

What is the role of the application layer in core banking architecture?

The application layer hosts core banking servers, interface servers, and ATM application servers. It handles business logic, user interfaces, and integration between channels and databases.

How are ATM transactions processed differently from other channel transactions?

ATM transactions use the ISO 8583 standard and connect to the ATM application server through the ESB, while other channels typically interact with the core banking system via REST or SOAP APIs.

What functions does the database layer serve in this architecture?

The database layer stores core banking data, manages documents for loans and customer applications, and supports monitoring and analytics through Prometheus and Grafana.

How is monitoring implemented in a core banking system?

Monitoring is performed using Prometheus, which scrapes metrics from application and database servers, and Grafana, which visualizes these metrics in dashboards for operational insights.

What methods are used to replicate data for reporting purposes?

Data can be replicated using Active Data Guard, Golden Gate, or SAN replication to maintain a reporting database that supports real-time analytics and reporting.

How do banks integrate SaaS applications like Salesforce with their core banking systems?

SaaS applications are integrated through middleware solutions such as Oracle Integration Cloud, which connects cloud-based systems to on-premise core banking applications.

What role do messaging systems like Kafka and IBM MQ play in core banking?

Kafka is used for publishing events, such as notifications to SMS or WhatsApp, while IBM MQ handles financial messaging like Swift MT/MX messages for interbank communication.

What is the purpose of a reporting layer in core banking architecture?

The reporting layer consolidates data from core banking and other systems into a reporting database or data warehouse, allowing analytical tools to generate enterprise-wide reports and insights.

Why might some business logic be implemented at the database layer instead of the application layer?

Some solutions offload certain processing tasks to the database layer to optimize performance, maintain data consistency, or leverage database-level procedures and triggers.