Frequently Asked Questions
What causes a core banking system to go offline repeatedly?
Repeated outages across a large branch and ATM network are usually a stack-wide problem, not a single point of failure — bandwidth saturation between branches and the data center, memory (heap) exhaustion on application servers under load, and inefficient database queries can each independently trigger downtime, and they often compound during peak transaction periods.
How was downtime eliminated for a bank running 3,000 branches and 10,000 ATMs?
Avekshaa audited the full transaction path — network bandwidth, application heap sizing, web and app server load balancing, front-end configuration, and database query performance — and implemented targeted fixes at each layer. Web server downtime, which previously occurred 3-4 times a day, was eliminated entirely.
What is heap analysis and why does it matter for banking systems?
Heap analysis examines how much memory an application server needs to handle expected transaction volume, and whether its current heap configuration is sized correctly. An undersized or misconfigured heap leads to excessive garbage collection, slow response times, and — at scale — server crashes under peak load.
How much did database performance improve in this case study?
Database performance tuning, including an overall database health check-up and identifying and tuning long-running queries, resulted in approximately 50% faster response times.
What technology stack was involved?
The stack included Finacle core banking software, an Oracle database running on Solaris, IBM WebSphere Application Server, and Resin web server.