Queues with Postgres - Goodbye SQS, RabbitMQ and Kafka

SQS, Kafka and RabbitMQ can go in the bin. With pgmq your message queue lives inside Postgres, in plain SQL: create a queue, send JSON, read with a visibility timeout, get exactly-once delivery. Then 100,000 messages and 100 workers hit a 2 CPU container to test whether "Postgres doesn't scale" holds up. 🔗 Relevant Links https://github.com/pgmq/pgmq ❤️ More about us Radically better observability stack: https://betterstack.com/ Written tutorials: https://betterstack.com/community/ Example projects: https://github.com/BetterStackHQ 📱 Socials Twitter: https://twitter.com/betterstackhq Instagram: https://www.instagram.com/betterstackhq/ TikTok: https://www.tiktok.com/@betterstack LinkedIn: https://www.linkedin.com/company/betterstack 📌 Chapters: 00:00 Queues inside Postgres 00:30 Setup with Docker 00:53 Create a queue 01:06 Send messages 01:18 Read messages and visibility timeout 01:43 Archive or delete 02:00 Stress test: 100,000 messages, 100 workers 02:44 Client libraries: TypeScript and Python 02:57 Wrap up