E-Ink News Daily

← Back to list

We used a database as a message queue. Now we use Kafka

Tigris explains why they migrated async task queues from FoundationDB to Kafka, citing read/write contention, expensive multi-write task operations, and custom implementation maintenance as key pain points. They moved garbage collection tasks to Kafka while keeping some queues in FDB, reducing operational complexity and load on their database.

Background

Tigris is a cloud storage platform backed by FoundationDB. The article discusses a common architecture dilemma where teams start by using their database as a message queue before outgrowing it.

Source
Lobsters
Published
Oct 1, 2026 at 04:28 AM
Score
6.0 / 10