4 ms·
You can just use MySQL as the backing store for the queue. I think pretty much all systems of a sufficient size end up reinventing this...
by joshu 18y ago
You can just use MySQL as the backing store for the queue.
I think pretty much all systems of a sufficient size end up reinventing this...
- aschobel 18y agoWe are using BDB, dead simple and insanely fast. Relational database seems a bit overkill.
- liuliu 18y agoIt seems that key-value database is still hot. Agree that "relational database seems a bit overkill". In fact, I am considering refactor a whole site to with key-value backend.
- joshu 18y agoIt may be overkill, but there is typically a great deal of expertise around setting up and running them. Also, MySQL etc have a great deal of network connectivity and concurrency support that is not provided by BDB. (In the mentioned example, they say they used PHP. Can you imagine doing concurrency in PHP?) So it's more a matter of expediency than aesthetics. At scale, everything is painful and you'd really rather not write anything you don't absolutely have to.
- jrockway 18y agoConcurrency is one of BDB's strongest points. (As for networking connectivity, BDB has an RPC server which works pretty well, although I'd personally probably roll something higher-level and stick that in front of the actual database.)
- aschobel 18y agoYep. We looked at the BDB's RPC system but are probably going to end up going with Thrift for RPC. Other than the lack of documentation, Thrift seems pretty killer.