It’s probably the tenth time I’m implementing something like this, and I’ve never been 100% happy about solutions I came up with.
The reason using mysql table instead of a ‘proper’ messaging system is attractive is primarily because most application already use some relational database for other stuff (which tends to be mysql for most of the stuff I’ve been doing), while very few applications use a messaging system. Also – relational databases have very strong ACID properties, while messaging systems often don’t.
The first idea is to use:
create table jobs( id auto_increment not null primary key, message text not null, process_id varbinary(255) null default null, key jobs_key(process_id) );
And then enqueue looks like this:
insert into jobs(message) values('blah blah');
And dequeue looks like this:
begin; select * from jobs where process_id is null order by id asc limit 1; update jobs set process_id = ? where id = ?; -- whatever i just got commit; -- return (id, message) to application, cleanup after done
Table and enqueue look nice, but dequeue kinda bothers me. How likely is it to rollback? Or to get blocked? What keys I should use to make it O(1)-ish?
Or is there any better solution that what I’m doing?
I’ve built a few message queuing systems and I’m not certain what type of message you’re referring to, but in the case of the dequeuing (is that a word?) I’ve done the same thing you’ve done. Your method looks simple, clean and solid. Not that my work is the best, but it’s proven very effective for large-monitoring for many sites. (error logging, mass email marketing campaigns, social networking notices)
My vote: no worries!