Understood. We use PostgreSQL as the default messaging queue for development configurations. Less moving parts than also running Redis (which is in production / staging and what the backend devs and contractors use locally).
It works, but I wouldn't want to put it into production. Our project is aimed for "internet scale" , and there are some intensive processes that are already taxing on Postgres quite a bit. we're actively migrating stuff off of PG and into graphing and "big data" systems. i could spin up another postgresql server to act as a queue. that should still worth with the two-phase commit in sqlalchemy / transaction. that could be the solution. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
