Geographically Distributed Prallel Databases - A Reality!
summary
TransLattice delivers a runnable geographically distributed OLTP database built as one ISO/OVA on Postgres92 + Postgres‑R with proprietary networking and storage. It claims active‑active, no‑master immediately consistent commits using a global commit order ID and a generalized Paxos consensus so transactions commit with quorum; reads can continue if a single copy exists. Sharding, policy‑based placement and redundancy (examples: three copies default, can set four copies across continents) migrate hot data, recover nodes in parallel, and let existing SQL apps run unchanged.
AI-written summary · about
chapters (8)
- 0:00Geographically distributed databases
- 2:38TransLattice Elastic Database vision
- 5:08TransLattice Elastic Database with PostgreSQL
- 10:13Data placement policies
- 15:32Application compatibility
- 19:02Redundancy and failure handling
- 24:18Benefits and deployment flexibility
- 25:35Q&A: Performance and sharding
related talks
59mTransLattice Elastic Database Architecture Deep Dive
48mOnline OLTP Computing and Traffic Governance as a Service for True Digital Transformatio
38mPostgreSQL as a distributed computing platform
13mOracle Globally Distributed Database
49mPostgreSQL’s Journey to Distributed Databases
29mModern Database Architecture: From SQL to NoSQL & Distributed SQL
50mSupersized Postgres: Postgres-XL for OLTP and Big Data Analytics
49mThe Paradigm Shift - Understanding the Move To Distributed Databases