Architecture of a Fintech Startup
summary
Stan builds a next‑gen capital platform and confronts heavy regulation and integration sprawl, with company onboarding split into 15 Steps and KYC/AML flows of 51 steps. Architecture focuses on layered domains and subsystems to reduce accidental complexity, enforces backward‑compatible DB and API migrations for rolling updates, and keeps services stateless or in distributed cache. Long business processes use Saga patterns and durable workflow engines (mentions Pence and empal style durable execution) while observability standardizes on open simetry and an allel collector.
AI-written summary · about
chapters (12)
- 0:00Introduction and Speaker Background
- 0:35Agenda Overview
- 0:54Understanding FinTech Startups
- 2:27Quality Attributes in FinTech
- 3:28Complexity in Systems
- 5:17Evolutionary Architecture
- 6:21System Topology and Dependencies
- 10:15Distributed Operations and Reliability
- 12:59High Availability Strategies
- 17:56Everyday SRE Practices
- 18:14Observability and Monitoring
- 23:03Conclusion and Summary
related talks
40mCAPtivating architecture: Navigating Distributed Systems and Microservices
42mStart As You Mean To Go On
15mCompliance-by-Construction for Credit Apps
51mScaling yout Architecture with Services and Events
35mEvent sourcing after page 1: How we built a cloud native bank
27mBuilding Microservices Architecture The Right Way based on Saga Pattern
24mPatterns of Evolution from Monolith to Microservices
04mDecentralized architecture patterns