Event language
UI language
Many teams reach for Kafka or RabbitMQ as soon as they hear the word “queue”,even when all they need is a simple, reliable background <a>worker. In </a>this talk, I'll show you how I solved trying not to unnecessarily complicated system. A real-world notification system is dissected where a custom queue was built entirely on PostgreSQL to handle 60K–130K notifications for nearly 30K users within minutes in production. The session walks through the core table design, partitioning strategy, and FOR UPDATE SKIP LOCKED worker pattern, then connects it to a rule-based notification architecture (manifest, generator, dispatcher) that stayed flexible enough to add new campaigns with configuration only.Attendees will see what went well, and where a Postgres-only approach is a good fit compared to dedicated messaging systems.
