← Thursday, October 1, 2026ArchitectureCase study

Tigris moves async task queues from FoundationDB to Kafka

tigrisdata.com 18 min read Editor score 8/10

Tigris kept queues in FoundationDB to preserve transactional writes, but task scheduling and completion added reads and writes that competed with user requests. The trade-offs show when a custom database-backed queue may stop scaling well for a growing product.

What

Tigris moved some asynchronous tasks, including garbage collection, from FoundationDB queues to Kafka while retaining queues in FoundationDB.

How

Using FoundationDB as a queue required scheduling writes and scans that competed with user requests, plus multiple writes per task.

Why it matters

Moving those tasks to Kafka reduces FoundationDB read and write load and cuts custom queue code.

Read on tigrisdata.com → Lobsters · 9 comments

Headline, summary, brief and diagram are written by a model from the source's own text; the link, byline and numbers come from the source. Read the original before relying on a claim.