







ParticleDB is a multi-model database designed for AI workloads. We tested versions 1.1.4 through 1.1.18.11.rc-22 and found that ParticleDB’s claims of “Full ACID” were somewhat premature. We present 96 issues in ParticleDB, ranging from the pedestrian (crashes, deadlocks, data loss, etc.) to the piquant (partially-invisible rows which could not be deleted, WHERE 4 = 5, dropped tables re-emerging in distorted forms, confused columns, strings turning into integers, and so on). Most issues required just a single server, single client, and no faults. By version 1.1.18.11.rc-22, all but ten of those issues appeared resolved. However, ParticleDB continued to lose committed writes during normal operation with the default occ transaction mode, and allowed internal anomalies and Lost Update with serializable, the strongest setting. Orkes, the makers of ParticleDB, have since released version 1.1.19-rc.13; they claim that it resolves all remaining issues discussed in this report. This research was funded by Orkes, Inc., and conducted in accordance with the Jepsen ethics policy.
Egres: A Postgres-compatible database for heavy, multi-tenant workloads
I love Postgres. It is an incredible database. But, its design is also 30 years old and most of what people fight in production comes from decisions made long time ago: VACUUM, transaction id wraparound, bloat, a process per connection…

Charly Wargnier on Twitter / X
an AI agent literally destroyed all of this guy's production data 🤯Total AI disaster, yet totally predictable.here's the story:> Cursor agent (Opus 4.6) tries to fix a staging bug> Finds an unscoped Railway CLI token> Guesses an API call> Wipes Prod DB & 3 mos of backups… https://t.co/24KfDhMtVz— Charly Wargnier (@DataChaz) April 27, 2026
AWS re:Invent 2018: Amazon DynamoDB Under the Hood: How We Built a Hyper-Scale Database (DAT321)
Postgres-backed Durable Workflow Execution | DBOS
Explaining the concept of a Postgres-backed durable execution system like DBOS and comparing it to external workflow orchestration systems like Temporal.

Artur Chakhvadze on Twitter / X
We are releasing our first quantized checkpoints for the Qwen3.5 series of models, co-designed jointly with our inference engine to achieve maximum possible performance on Apple hardwareStarting from 0.8B, 2B and 4B modelshttps://t.co/2R8BdhAfzv— Artur Chakhvadze (@norpadon) June 8, 2026
jazware/vlpds
Very Large PDS, a world-scale, incredibly efficient, incredibly resilient, atproto personal data server
SQL Workbench - Free Online SQL Editor and Workbench | Query local & remote CSV, Parquet and JSON data
Free browser-based SQL editor powered by DuckDB. Query and visualize CSV, JSON, Parquet and Arrow files locally or from remote URLs. No installation required.

Ollama Out-of-Bounds Read Vulnerability Allows Remote Process Memory Leak
Critical out-of-bounds read in Ollama before 0.17.1 leaks process memory including API keys from over 300000 servers via crafted GGUF files.

onyx-platform/onyx
Distributed, masterless, high performance, fault tolerant data processing
Free Electron
There's a Screwed Scenario that I missed. Back in my Borland days, we were working hard on Paradox for Windows. I was a QA engineer testing the database crea
Karpathy's Autoresearch found a 3-year-old bug in our query engine (and improved performance by 11%) - PostHog
A few weeks ago at a team offsite in Lisbon, we pointed an AI agent at our query engine, fed it slow queries from production, and let it run overnight…

Honker
Durable queues, streams, pub/sub, and time-trigger scheduling on SQLite. One file, zero servers.

TigerBeetle
The financial transactions database to power the next 30 years of Online Transaction Processing.
