News for hackers. Stuff that matters.
Re:Don't Use an RDBMS for Messaging by vidarh on Sunday September 28, 2014 @07:49AM (#8379500)
There's lots of stuff that is relational about jobs the moment you have a large number of them, and need to be able to search and filter by different statuses, different users, different sources, date and time, type of job etc., or run reports over them (how many percent of jobs are in what states? average latency to start processing? average latency to completion?)

You can work around that by putting metadata about the jobs into an RDBMS, or collating it separately, so you can certainly make do without an RDBMS...

Or you could just put them in the RDBMS in the first place and place a few indexes and optionally triggers to create log entries on state changes.

Re:Don't Use an RDBMS for Messaging by jeremyjh on Sunday September 28, 2014 @11:22AM (#8379947)
These all sound like attributes of a job definition - not separate entities to which a job is related. You are correct they would need to be indexed.