PoppyDB Goes Live — Measurements from a Real Bus

We have never been this far: PoppyDB went live. On a real message bus, three nodes, MongoDB replaced in the same spot. And this time it was about measuring, not bug-hunting. Result: roughly 14 percent more throughput, latencies a third to 40 percent lower, peaks down 83 percent. Bus timeouts from 50 to zero. Slow queries from nearly 30,000 to 17. Plus the backstory: 16 releases from 6.3.0 to 6.3.15 in two and a half months, every number fed back.

Morphium 6.3.15 — and the whole 6.3 series

Morphium 6.3.15 is out! The release that has been running in production on our message bus since October 21st. But really we celebrate the whole series: sixteen releases in two and a half months. From 6.3.0 (Aug 9) to 6.3.15 (Oct 21). Every measurement fed back into a small release. Highlights: 6.3.7/6.3.8 "bugs we all had", the SCRAM fix in 6.3.12, the replication flow control in 6.3.14. And 6.3.13? It does not exist. Halloween. 😉

Morphium 6.3.7 and 6.3.8: Bugs We All Had

Last time it was about bugs nobody ever hit. Morphium 6.3.7 and 6.3.8 are the opposite: bugs we all had, for months, some for years. Found because we put PoppyDB onto a real message bus and looked properly - heap histograms, connection counters, logs. One Double per event that never goes away. 937,000 TCP connections in 61 hours for a client with nothing to do. A watchdog with 2,229 false alarms in a week. And a full-cluster restart that shows why a rolling restart is worthless as a test for restore paths.

Morphium 6.3.1 — and the Transparent Message Bus

We just released Morphium 6.3.1 - officially a bugfix release, in reality the harvest of 6.3.0's first two production weeks: server-side topic filters in the change stream, detection of mixed messaging implementations, and an in-memory driver that now behaves like mongod down to event ordering. And the occasion for the bigger story: why a message bus made of documents is transparent - with a peeker that reads along without consuming, and Morpheus as the cockpit for the running bus. Try that with Kafka 😉

Morphium 6.3.0 — What's New?

Morphium 6.3.0 — What's New?

The largest release in the 6.x line so far. Its centre of gravity is not the client this time — it is PoppyDB and the in-memory driver underneath it, both of which went from "good enough to run your tests against" to something you can actually operate.

Using a wire proxy to do failover tests

Failover testing with `kill -9` is manual labor and never runs in CI — yet from a driver's perspective, failover bugs are pure wire phenomena. So we moved the faults onto the wire: one TCP proxy per replica set node that can freeze, reset, or cleanly close connections, plus `hello` rewriting so the driver never sees the real addresses. The harness promptly found real bugs — including a read that spent 26 seconds hammering a dead primary.

Morphium 6.2.5: The One-Document Batch That Cost 20 Seconds

Morphium 6.2.5 is out. A quiet patch release with one loud story: a hardcoded change stream `batchSize=1` that turned into 20-second latency spikes over a high-latency link — plus Atlas TXT seedlist support, Quarkus native-image pre-registration, and a batch of InMemoryDriver and aggregation fixes.

Morphium v6 Performance — MongoDB vs PoppyDB vs InMemory

Morphium v6 rewrote the connection pool and messaging system from scratch. Here are the numbers: 38% more throughput, 2.5x faster messaging with PoppyDB, and a test suite that runs 879 tests across 5 backends in under an hour. --- id: 10647 ---

Morphium 6.2.2 — Bugfix Release with PoppyDB Hardening and Performance

Morphium 6.2.2 is here — a focused bugfix release that makes PoppyDB significantly more stable. Wire protocol corruption, thread leaks with 20,000 threads per node, and Raft election flapping are fixed. Plus: 4.7x faster startup via ClassGraph caching and PoppyDB is now 3x faster than MongoDB for individual operations.