Amazon Simple Queue Service (SQS) vs. TIBCO Messaging

While we use AmazonSimple Queue Service (SQS) in our serverless applications, it would be a great option to handle queue management for any internet-connect application. It provides the most benefit in situations where your application or service must maintain mission-critical queue of messages or jobs. If you're already using other AWS services you will find the greatest benefit.

Incentivized

Organization which uses TIBCO Business Works or TIBCO Business Process Management or TIBCO BPM Enterprise can make use of TIBCO Messaging as it works well with other TIBCO tools. Many TIBCO tools have TIBCO Messaging products bundled as a package along with other TIBCO tools. Use of dynamic topics and queues makes run time processing easier.

Incentivized

• SQS is reliable and fully managed. Our engineers do not have to worry about running RabbitMQ.
• SQS is very inexpensive.
• SQS allows data to be encrypted in transit, which may be required for compliance in some products.
• FIFO queues provide exactly-once processing.

Incentivized

• Tibco EMS performs very well, and it meets our stringent performance requirements for corporate messaging backbone.
• Tibco EMS scales well, and this is another of our stringent requirements.
• Tibco provides good support for the EMS product, and continues to improve it. This is important as we don't want to use something that does not keep up with the changes in the technology landscape.

Incentivized

• More frequest polling will be expensive
• No detailed monitoring of queues, just current data and regular monitoring is present
• No way to fetch messages back from the queue

• A bit of lag time between data sync and the data reaching the server for some of our field sites.
• It still seems like a niche product for me with little community support. I didn't know about it before working for a company that deployed it.
• Certain functionality is too complex to setup as compared to other products on the market.

Incentivized

EMS is a solid system and I see no reason to abandon it, in fact I am eager to see what the next versions will offer and future road maps. Knowing we have support to help us in case of problems is invaluable, both in case of critical issues and to improve overall performance.

Incentivized

Online blogging and documentation for SQS is great. There are many examples of implementing it and if you look hard enough, more than likely there are examples that meet the exact case with which you are working

Incentivized

To be blunt: Amazon SQS was the simplest to implement given our requirements. Other services in this space work just as well, and SQS does not have any benefits outside of being the easiest to implement when using an otherwise fully AWS stack. AWS itself even has other solutions that would work just as well, however, SQS had the most reasonable pricing model for our given situation. That will certainly not always be the case, but in several of the instances where we are using it, it just made the most sense.

Incentivized

We chose TIBCO Messaging not just for its performance but because it looked like the natural way to pave our existing TIBCO Integration architecture. Setting up TIBCO EMS servers and objects seems more straightforward than with most of competitors. It is easy to configure and easy to use and understand.

Incentivized

• Under the AWS Echo system, it provides great operating power to the application.
• The cost is much less for messages, and it also supports a multi-user option.
• Not for us, but for a larger organization, low throughput might become an issue for a standard queue type.

Incentivized

• Improved developer productivity as TIBCO Enterprise Message Service requires minimal coding
• Quicker time to market as the configuration / onboarding can be automated with this tool
• Ability to onboard more clients/consumers as the tool can handle large volumes seamless
• Improved visibility on the end to end process as the product provides monitoring by using JMS header information