Re:Show HN: Martinet – Distributed Task Queue for Node.js
by bhouston on Monday August 18, 2014 @08:00PM
(#8195348)
Using a database as the backend of the queue is a really good idea. Of course if you have a lot of load you can add a redis cache in front, but persistence and reliability of the queue data is highly important.
If not a DB, how else do you get consistency, reliability and ease of development? Basically you will end up re-implementing a database anyway.
PS. I wrote a highly popular render manager / queuer and I first ended up writing a custom database, but eventually the core was replaced with MongoDB and it is now even more scalable and robust.
If not a DB, how else do you get consistency, reliability and ease of development? Basically you will end up re-implementing a database anyway.
PS. I wrote a highly popular render manager / queuer and I first ended up writing a custom database, but eventually the core was replaced with MongoDB and it is now even more scalable and robust.