We used a database as a message queue. Now we use Kafka
bootlegbilly
13 points
1 comment
September 30, 2026
Related Discussions
Found 5 related stories in 124.7ms across 12,728 title embeddings via pgvector HNSW
- Scaling and benchmarking a critical message bus using a new indexing strategy eatonphil · 35 pts · October 08, 2026 · 50% similar
- How we built a proxy to migrate Kafka producers with zero downtime exposition · 20 pts · August 21, 2026 · 46% similar
- Making Postgres queues scale KraftyOne · 110 pts · July 30, 2026 · 46% similar
- BtrLog: Low-Latency Logging for Cloud Database Systems to_ziegler · 19 pts · August 27, 2026 · 46% similar
- Apache Kafka vs. Apache Iggy: A Technical Comparision mmatloka · 12 pts · September 02, 2026 · 45% similar
Discussion Highlights (1 comments)
linehedonist
"FoundationDB was our only database, queue included. We built Apple's QuiCK design on top of it, hit the write limits, and moved async tasks to Kafka." very LLM-y.