Message queues are great whenever you don’t have a permanent connection or are working in loosely coupled situations. They’re also handy when you simply want to dump your input and return to your application without waiting for the output from whatever application or server will be processing your input. You can make message queues the basis of a fail-safe application that uses them whenever your regular database fails. This can help ensure that no data is lost and you have very little or no downtime at all, if you use transactional queues. Obviously not all applications can use message queues to such advantage, but for storing or accepting customer input it can be a great solution. One example springs to mind that wouldn’t benefit from using message queues, and that is a banking transaction that needs to be processed in real time.
KeywordsComputer Management Database Program Internal Transaction Local Machine Encrypt Message
Unable to display preview. Download preview PDF.