> just be aware that you're going to need to rethink some of your architectural foundation if/when you need to move to a higher-throughput queue implementation

> just be aware that you're going to need to rethink some of your architectural foundation if/when you need to move to a higher-throughput queue implementation I haven't seen many if any projects that didn't require some architectural rethinking over their lifetime. I have seen more, that where arguably over engineered in the beginning, but then never lived long enough to actually benefit from it. Not saying everyone should use Postgres-as-queue for every project. But for a lot of projects it is going to be much harder to acquire the active user base generating the throughput Postgres can't handle, than doing continuous refactoring of the system to deal with the changing requirements.