Platform Engineering for FinTech
summary
Claims concrete architecture choices: user-based sharding for single-account ops, synchronous in-region / asynchronous cross-region replication for accuracy plus global scale, and Kafka event streaming for audit-friendly event sourcing. High-frequency trading case studies report microsecond execution and sub-millisecond monitoring, a digital bank handles millions of concurrent users, and a payment processor achieves subsecond authorizations. Operational pain points include automated shard rebalancing, replication lag monitoring, and cross-shard transaction coordination, all shown working in production.
AI-written summary · about
chapters (11)
- 0:00Introduction to Platform Engineering in FinTech
- 0:57Agenda Overview
- 2:12Evolution of Financial Infrastructure
- 4:36Database Sharding Strategies
- 6:46Replication Models for High Availability
- 8:58Consistency Models in Financial Systems
- 9:45Architectural Patterns for Scalability
- 11:35Security and Compliance in FinTech
- 12:35Case Studies and Real-World Implementations
- 13:42Future Directions in Financial Platform Engineering
- 14:29Conclusion
related talks
54m$10K per Minute of Downtime: Architecture, Queues, Streaming and Fintech
14mArchitecting Secure and Scalable Integration Platforms for FinTech
25mPlatform Engineering in Financial Institutions: The Practitioner Panel
13mBuilding Financial Fortresses: Real-Time Fraud Detection
10mBuilding High-Performance Financial Data Pipelines
23mScalable Architecture for Processing UPI Real-Time Transactions Using Distributed SQL
25mHow Sharekhan Scaled Trading Platform with Yugabyte's Distributed SQL
40mDistributed Commit Log: Application Techniques for Transaction Processing