top | item 46447788

(no title)

dmarwicke | 2 months ago

why postgres for this? feels heavy for a queue. tried something similar with redis and it was way simpler

discuss

order

mehdig10|2 months ago

Well yeah for a simple queue where messages live in memory and disappear once consumed there are plenty of technologies that work (rabbitmq, redis...). Here is the goal is not to just build a queue but rather have something persisted where you can inspect payload and replay even days after the original even was sent