Kafka

Your Database Is Already a Better Message Queue Than Kafka. Here’s Why.

Conventional wisdom says databases can’t handle queues. That was a lie from 2012. Modern Postgres, with SKIP LOCKED and LISTEN/NOTIFY, can handle tens of thousands of messages per second, eliminating the need for separate message brokers like Kafka or Redis for most applications. The real cost of adding a separate queue is operational complexity and transactional inconsistency. Stop adding infrastructure. Use what you already own.

Kafka Compacted Topics Are a Lie. Here’s the Truth.

Kafka compacted topics aren’t a streaming pattern β€” they’re a distributed key-value store with a garbage collector that silently erases your history. KGazer exposes this duality by storing the full evolution of state in PostgreSQL, giving you a browsable, queryable time machine for every key. If you’ve ever tried to reconstruct what a compacted topic looked like three hours ago, this is the tool you didn’t know you needed.

You’re Wrong About Postgres LISTEN/NOTIFY. It Actually Scales.

You’ve been told Postgres LISTEN/NOTIFY doesn’t scale and that you need Kafka for real workloads. The data proves otherwise: it handles 60K+ notifications per second. The bottleneck isn’t the databaseβ€”it’s developers misusing it as a message bus. Send an ID, not a payload, and watch it thrive.