2 ms·
This one time I had to work at a place where a postgresql install was not only the main datastore, it was also the main system message bus by abusing notifies.
by sophacles 17y ago
This one time I had to work at a place where a postgresql install was not only the main datastore, it was also the main system message bus by abusing notifies. Further the enterprise message bus was a homebrew thing that was written to both pass messages and do RPC, oh and be the main way to monitor if a remote site was up or not. I think both of those count as well.
For those who are curious: given these were linux systems, d-bus was the right answer for the former, and something like RabbitMQ or OpenAMQP, or even JMS solutions would be the proper answer to the latter.
- gaius 17y agoSee to me, those look like homebrew solutions, and Tibco/RV or MQSeries is the proper answer. It's easy in retrospect, but Postgres predates JMS etc by a loooong way - who's to say that wasn't the best solution at the time?
- sophacles 17y agoGood question! The postgres solution was unexcusable, it was always used side-by-side with dbus. The other was around before any affordable[1] enterprise message busses existed, however as that changed the buggy solutions was still touted as "amazing new tech that keeps us ahead ofthe competion. No we can't switch to something else". [1] Affordable being defined as: this particular company could pay for it without going out of business.
- deleted 17y ago[deleted]