{"repo":"MartinKalema/horizontal-scaling-convex","free":true,"listed":false,"github":"https://github.com/MartinKalema/horizontal-scaling-convex","clone":"git clone https://github.com/MartinKalema/horizontal-scaling-convex.git","description":"Experimental Convex backend fork aiming to scale Convex horizontally while preserving its core semantics: reactive subscriptions, serializable transactions, and consistent snapshots.","language":"Rust","stars":23,"topics":["convex","distributed-systems","horizontal-scaling","nats-jetstream","open-source","postgresql","real-time","rust","distributed-database","replication"],"license":null,"category":"databases-storage","readme_excerpt":"Horizontal Scaling for Convex Experimental fork of the Convex open-source backend aiming to scale Convex horizontally while preserving the things that make Convex Convex: - reactive subscriptions; - serializable transactions with optimistic conflict detection; - consistent snapshots; - TypeScript functions running against a database-like execution model; - developer APIs that do not expose partitions, leaders, placement versions, or routing details. This project is currently an alpha distributed-systems hardening effort . It has working clustered read/write scaling milestones, Raft-backed partition durability, two-phase commit, NATS JetStream replication, and a growing correctness test suite. It should be treated as research-grade clustered infrastructure while the remaining correctness and operations roadmap is completed. Latest milestone: v2.1.0-alpha.1: Distributed Correctness Hardening Why This Exists Convex is a reactive database. The backend keeps live state in memory, tracks query dependencies, retries conflicting mutations, and pushes subscription updates in real time. That model is powerful, but the self-hosted backend is single-node by design. The hard part is not just \"add sharding.\" A useful horizontally scaled Convex must preserve the same high-level semantics developers expect from Convex: - subscriptions should remain correct and current; - transactions should remain serializable; - queries should observe consistent snapshots; - clients should not have to know ","default_branch":null,"files":null,"tree":[],"storefront":"/r/MartinKalema","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/MartinKalema/horizontal-scaling-convex/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}