Yeeting over 30k messages per second on Postgres with Tembo MQ(tembo.io)
tembo.io
Yeeting over 30k messages per second on Postgres with Tembo MQ
https://tembo.io/blog/mq-stack-benchmarking/
7 comments
Love seeing a whole new generation of companies, like Tembo, laser-focused not only on breaking PostgreSQL down to it's basic building blocks but also on all PG extensions that are out, many of which are 10+ years old, of mixed quality, and then going super deep on improving them, re-architecting them for modern workloads ("Twitter Scale as described in this blog post) with the idea there are enormous amounts of performance gains and/or efficiencies to be gained.
Thanks - sort of boring what we're doing (on the surface) but there is so much goodness inside the Postgres ecosystem that deserves celebration and polish. It's an amazing community to spend time in.
Tembo has been on a tear. Consistently focusing on making the developer experience better and delivering capabilities that really move the needle.
There is so much untapped potential for Postgres. It is so widely used but most folks only scratch the surface in what it can do. I only recently learned about how many extensions exist but since many are pet projects, the creators haven't really focused on how to make them more effective or tackle more use cases beyond their own.
There is so much untapped potential for Postgres. It is so widely used but most folks only scratch the surface in what it can do. I only recently learned about how many extensions exist but since many are pet projects, the creators haven't really focused on how to make them more effective or tackle more use cases beyond their own.
The team at Tembo keeps working quickly to enable many different use cases with Postgres and extensions. Pretty fun example of how capable Postgres is for various tasks.
Thank you! We built PGMQ because we needed a queue to sit in between our managed service's control-plane and data-plane. We made it an extension so that it became a feature of the database, which meant we could use it with any programming language. IMO, this is a benefit of Postgres extensions that often gets overlooked...any language with a Postgres driver can use Postgres extensions.
The Trunk registry[1] that they support is also super interesting, nice to see all Postgres extensions in one place
[1]: https://pgt.dev/
[1]: https://pgt.dev/
That's very cool