Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • We did look into a queue system, but abandoned the idea and instead chose to use a database. One of the reason being, the only queue system in our enterprise mature enough for our purpose is one, we do not wish to create a dependency to - due to license costs. Commented Jul 24, 2018 at 10:06
  • @KelvinWayne, you're not able to just run an ActiveMQ server (it's open source) or something? It really sucks when the right technology exists, but you can't use it due to arbitrary constraints. Maybe look into ways you can implement a queue on a database using careful locking? Commented Jul 25, 2018 at 0:48
  • I could, however the scale we will be running it at would require a complex installation that needs to be maintained, regardless of whether we chose RabbitMQ, ActiveMQ or some other free technologoy. We also looked at cloud paas solutions, however they do not (yet) provide selector filters. Commented Jul 25, 2018 at 10:26
  • If we were to use a queue system, we also have WebSphere MQ on Z/OS but due to multiple reasons, we have decided to use a DB. We already have multiple DBAs and a Always On Availability Group MSSQL cluster setup, so even though you are right in terms of technology match, using a DB is a better match for our corporation. Commented Jul 25, 2018 at 10:26