Database
The Case for Single-Version Concurrency Control in the Cloud
arXiv cs.DB0 views
arXiv:2610.15793v2 Announce Type: replace Abstract: Multi-version concurrency control (MVCC) has been the dominant concurrency protocol in modern database management systems (DBMSs). However, cloud-native HTAP architectures shift many of MVCC's traditional advantages from the primary transaction engine to the deployment architecture. Now, transactional and analytical processing are decoupled into loosely synchronized engines, while cloud deployment primitives provide the workload isolation required for this design. In this paper, we challenge the status quo, arguing that single-version concurrency control (SVCC) is better suited to cloud transaction processing than MVCC. Through a systematic analysis of MVCC's limitations, we show that SVCC avoids these shortcomings through a more lightweight and efficient design. Beyond arguing for a lighter transaction processing, we use this SVCC effort as a blueprint to advocate for a broader rethinking of cloud-native architectures and to outline a research roadmap to shape next-generation DBMSs.
Source:https://arxiv.org/abs/2610.15793PreviousTEAR: Table Extraction with Attribute Recommendation from Texts via Large Language ModelsNextAn Iterative LangGraph Agent for Text-to-SQL: Natural Language Access to the Chicago Crime Database
Related posts
How to upgrade Postgres in Docker to 18, and be ready for 19: dump and restore or pg_upgrade --link
0dev.to Docker
Docker Compose: Run Your App and Its Dependencies Together
0dev.to Docker
Show HN: Vaire, Self-Hosting Postgres Through the One Glorious CLI
0Hacker News Show
Gabriele Bartolini: CloudNativePG reaches CNCF Incubation: another rung on the ladder
0Planet PostgreSQL
pandas chunks fixed my memory error, then quietly broke my averages
0dev.to
Postgres LISTEN/NOTIFY vs Redis Pub/Sub: Latency, Write Cost and Failure Cases, Tested
0dev.to Node