Fault-Tolerant Architecture of a Bank's Front-End System
summary
A talk about building a fault-tolerant front-end system for a bank, explaining how a bank’s high-load front-end differs from a typical web project and where it sits in the bank’s IT landscape. It describes scaling databases in an enterprise where vendor solutions are limited—using sharding by database instances—and achieving high availability by partitioning web servers and application servers into loosely coupled blocks that each serve a subset of clients and fail over to reserves when a block goes down.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 4:19Multi-tenant architecture
- 14:07Handling external failures
- 18:41Limitations and fraud
- 19:01New architecture challenges
- 27:27Improving fault tolerance
- 28:30Q&A
related talks
36mDesigning for failure - architecting fault-tolerant system
34mBuilding High Resiliency into Digital Solutions
15mPlatform Engineering for FinTech
54m$10K per Minute of Downtime: Architecture, Queues, Streaming and Fintech
03mThe evolution and future of software architecture
52mDatabase sharding at the load balancer level
08mWhen Worlds Collide: Frontend vs Database
48mIT Architecture : All your micro-services are wrong PERIOD!