Amazon Simple Queue Service (SQS) vs. TIBCO BusinessEvents

If you are looking to build something that just requires a simple queue service (as the name implies) this is great for it. You might look elsewhere though if you get into more complicated needs. This is also very well suited if you are already using other services with AWS and intend to fully build whatever you are building in AWS. If you are looking for a mixed environment -- SQS is not for you

Incentivized

TIBCO BusinessEvents is part of the CEP (Complex Event Processing) family, this means that it fits perfectly in all those scenarios where a correlation between incoming events is required. Where a stateful process is necessary. It does not fit well for a kind of Process Orchestrator scope, where simple events are coming in, and there is a well-defined behavior the system, would have on incoming request, and no particular reason to use a rule engine and its complexity. Anyway, there are particular cases where BusinessEvents would be a good actor in orchestrating a portion of CEP solutions activities

Incentivized

• It provides an always-available serverless queue for workflows or mission-critical processes.
• Is extremely low cost and overall costs to our environments have been negligible.

Incentivized

• It allows us to build rule-based model-driven application, to collect, filter, analyze, correlate various business events in our real-time event flow
• It makes various business applications/components easy to integrate (loosely decoupled but chained via the events flow) together
• Its distributed rule engine and embedded in-memory data grid (ActiveSpace) gives us a lot of flexibility and room to play with a large amount of rules and data with high performance

Incentivized

• Almost all of the functionality has been covered by SQS, but they could improve the throughput time.
• Also, they could provide built-in Cloud Watch, so that we can easily configure it without any external efforts.

Incentivized

• Better integration with R versions and better debug for R-scripts in Spotfire. There are inconsistencies in syntactic expressions accepted by R-studio and not accepted in Spotfire. Accelerating the debug would be awesome. Having a command like View (data frame) that directly output in the dashboard would be a great accelerator.

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

The most comparable products are RabbitMQ, and perhaps ActiveMQ. Until recently, AWS did not offer a managed ActiveMQ product. Running RabbitMQ will never be to my team's competitive advantage; we wanted a managed service.

Incentivized

I was not part of evaluation of the products in this space in my organization. But I feel BE is better in terms of RIO if compared with some commercial products from Orcle, IBM and SAP. I strongly feel difficulty in using cloud native features is one big shortcoming in current product offering. This will tend customer like us to explore options that are well suited with ur cloud first vision.

Incentivized

• Positive impact - time allocation towards different features
• Negative impact - too many resources dedicated towards debugging
• Positive impact - less manual labor during testing

Incentivized

• Positive : Real-time event stream processing helps handle transactions very efficiently.
• Negative : Earlier versions of BE (5.0 & 5.1) had major issues in data handling in cache that impacted the data integrity of the application.
• Positive : Decision Tables are a huge plus in TIBCO BE.

Incentivized