News for hackers. Stuff that matters.
Re:Asynchronous Processing in Web Apps, Part 1: A Database I... by icebraining on Thursday November 15, 2012 @07:45AM (#4788272)
With a traditional database this typically means a service that is constantly querying for new processing tasks or messages.

Traditionally, but not necessarily; PostgreSQL supports the LISTEN and NOTIFY commands for asynchronous notifications, without polling.

Re:Asynchronous Processing in Web Apps, Part 1: A Database I... by nesquena on Thursday November 15, 2012 @02:56PM (#4790430)
I agree and if polling was the only consideration then this would mitigate the issue. Admittedly I didn't cover this as much in my article but there's also a lot of other flexibility afforded by a good message queue around delivery strategies, consumption strategies, error handling, etc that you would have to do much more manually and painfully trying to shoehorn it into a database (even a good one). I am not saying PostgreSQL notify commands are not useful for certain tasks, just encouraging people to understand the tools available and pick the right one for the job.
Re:Asynchronous Processing in Web Apps, Part 1: A Database I... by lvh on Thursday November 15, 2012 @10:04AM (#4788829)
Also, Axiom, my favorite little Python object layer over SQLite, has native scheduler support. Whenever loading a store (well, starting the store's scheduler service), all things-to-happen are scheduled to run using Twisted's event loop. And, well, event loops are very good at efficiently waiting for things to be done in the future :)
Re:Asynchronous Processing in Web Apps, Part 1: A Database I... by joevandyk on Thursday November 15, 2012 @01:27PM (#4789951)
queue_classic is a postgresql job queue that can use listen/notify. http://www.postgresql.org/docs/9.1/static/sql-notify.html

Although queue_classic doesn't use listen/notify by default, and I'm not sure why. I think it should, it seems to perform better.