How fast can a message queue on Postgres be? Pretty fast, as it turns out. Today Adam gives a quick demo of just how fast Postgres + pgmq can fly through a backlog of messages.
if I were to add a mesage que for real time OLTP database workloads, would that also induce latency which makes the OLTP database workload not in real time anymore? if so then whats the point of message queues then if its going to be used in real time OLTP database workloads?
@@jirehla-ab1671 : Several people already use external message queues before they write data to their databases or to send data to multiple sources like your OLTP database and your analytics database. Having that within Postgres reduces the latency compared to external message queues as the data is already in Postgres and is near your primary data store.
Nice performance, but that's definitely not a small server.
Want to know more? Check out the blog here: tembo.io/blog/mq-stack-benchmarking
if I were to add a mesage que for real time OLTP database workloads, would that also induce latency which makes the OLTP database workload not in real time anymore? if so then whats the point of message queues then if its going to be used in real time OLTP database workloads?
@@jirehla-ab1671 : Several people already use external message queues before they write data to their databases or to send data to multiple sources like your OLTP database and your analytics database. Having that within Postgres reduces the latency compared to external message queues as the data is already in Postgres and is near your primary data store.
But it isn't webscale like mongo db
i'd argue that postgres is webscale