People are similar to water: they will often the path of least resistance. The trick is to find a solution, document its “shape”, make it easy to integrate and

People are similar to water: they will often the path of least resistance. The trick is to find a solution, document its “shape”, make it easy to integrate and market the hell out of it internally. Then you let the market decide. Building a big shared common library can be a mistake, but that’s not because it’s intrinsically the wrong choice, it’s impact is partly a function of how many resources you can dedicate to effectively designing and maintaining it. At a certain scale the economics of this suddenly flips. The problem in the post seems to scream infrastructure rather than code. Identify the different types of queues services need, pick some off the shelf and preferably managed solutions, then make it take 5 minutes to get started.