Building a resilient system with Frappe and Kubernetes
summary
Architecture moves from a monolith to Kubernetes-managed runtimes, decoupling web workers, background workers, Socket.IO and file storage and running multiple Frappe runtimes as microservices; reads go to replicas while critical writes move to dedicated primaries and sharded databases; file storage shifts to Azure Blob storage, caching uses cache sharding and pooling, and the platform sustains 1.2M shipments/day across 300+ warehouses with isolated replicas and no major blockers.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:05Monolith Architecture
- 3:27Decouple Runtimes
- 5:26Segregation
- 8:53Doctype
- 9:53Cache
- 10:59Replica Isolation
- 12:27segregation of write operations
- 14:35microservice
- 16:31sharding
related talks
51mCompetitive retail architecture with microservices
45mRunning a Real-World, Mission-Critical System on Azure
14mTransforming the Omni-Channel Experience at Kroger
14mKeynote: The Big Leap: Conquering the Legacy System and Building a Scalable Cloud Infra...
20mThe Future of Databases
19mKeynote: From COBOL to Kubernetes: A 250 Year Old Bank's Cloud-Native Journey
20mBuilding the Future How We Created Our New Platform For Growth
31mDevOps in the Cloud: Case Studies of Amazon.com teams and their resilient architectures