2 ms·
I've decided to implement in an RDBMS, partly because this will allow me to become familiar with the concepts of message queues at a much lower level. I'm goin
by kbenson 14y ago
I've decided to implement in an RDBMS, partly because this will allow me to become familiar with the concepts of message queues at a much lower level. I'm going to try to provide a semi-generic solution so the result is usable for more than my initial implementation, but I think this will provide the most benefit to both my employer and myself. I'll be intimately familiar with the core concepts, and will then know how to parse the feature/capability lists of the various implementation available, and will then be able to make an informed decision if I need to replace the system later.
I like how writing about it forces me to crytalize my thoughts, so I'm going to write it up[1].
[1]: http://yaketyhack.blogspot.com/2013/04/rolling-your-own-messagejob-queue-in.html http://yaketyhack.blogspot.com/2013/04/rolling-your-own-mess...
P.S. I've used a similar technique before in the absence of a reliable recommendation on a technology, due to unknown constraints or otherwise. The result of that was "Don't write your own ORM if you can avoid it (unless it's just to learn)". We'll see if the same result applies here...