How do you cut a monolith in half?
After reading Enterprise Integration Patterns [1] a few years ago, I've been under the impression that message queues are the holy grail for decoupling systems that you want to pull apart, but this offers a really nice perspective on where they might not be a panacea. Thank you!<p>There's a couple of nice ideas in here (the "message pump" for one at least) that I'm going to steal and use at work. It's also comforting to know that we're not completely crazy for using a DB to store tasks/processes that need to be run and retried if necessary instead of a message queue.<p>[1] <a href="https://en.wikipedia.org/wiki/Enterprise_Integration_Patterns" rel="nofollow">https://en.wikipedia.org/wiki/Enterprise_Integration_Pattern...</a>