How to design a DBMS for Telco requirements
14 days ago
- #Telco
- #DBMS
- #High Availability
- Evolution of DBMSs and relation to Google Spanner, Aurora, PolarDB, and MySQL NDB Cluster.
- Design considerations for Telco DBMS: high availability, distributed architecture, and in-memory processing.
- Challenges with Shared Disk DBMS and advantages of Shared Nothing DBMS for Telco requirements.
- Replication strategies in Shared Nothing DBMS: immediate REDO log application for minimal downtime.
- Handling failures: heartbeat protocols, non-blocking 2PC, and leader-selection algorithms.
- Key design principles for Telco DBMS: in-memory, Shared Nothing, immediate replication, and high concurrency.
- MySQL NDB Cluster's 20+ years of high availability and its adaptation into RonDB for modern AI platforms.
- RonDB's improvements: ease-of-use, scalable reads, new interfaces (REST, RonSQL, Rondis), and managed services.