Hi Andrew, Yup, I think my mind is made up...I will use SQLite with WAL with "fairly frequent" commits to force the update of the database from the WAL file.
How often do you run the commits between the two files? Or do you just use the default? Chat later Lynton -----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Andrew Davison Sent: 01 October 2010 12:43 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] SQLite is perfect for FILE based MESSAGE QUEUE? I've used SQLite for exactly this. I have no gripes with it at all. I ended up using just one table in one DB as indexing makes things simple and fast and I support arbitrary queues with multiple readers. WAL i've been trying these last few days and seems trouble-free. On 30/09/2010 6:11 PM, Lynton Grice wrote: > Hi there, > > > > I am a HUGE SQLite fan and have an interesting question I have been > scratching my head about for a couple days now. > > > > First off my daily job is very much around "messaging" and I am very > familiar with message queue products like Websphere MQ and Fiorano MQ. > > > > When you install Websphere MQ or Fiorano MQ they have a FILE based queue > underneath by default (typically one file per queue with the messages etc > stored at different offsets). > > > > There messaging systems will have "file writer locks" that in essence will > only allow ONE WRITER per queue at any one time. So any clients sending > messages will have "to wait in line" until the message can be physically > written to file. > > > > Bottomline: We have one writer and multiple readers per queue....fine. > > > > Then I scratch my head and wonder why SQLite is not the PERFECT persistence > layer for building an awesome "file based queue" on? It is lightening fast > by default, and also has the same "locking issues" described above. We are > talking milliseconds anyway....between writes.... > > > > Bottomline: Is there any reason why anyone would think someone like me > coding a solid message queue using SQLite is a bad idea? Am I missing > something? I personally think it is a wonderful idea and would be hugely > useful to my daily job.... > > > > Any help or advise in this regard would be hugely appreciated ;-) > > > > Thanks > > > > Lynton > > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
