TIBCO Integration (including BusinessWorks and Flogo)

Anything integration

When workflows come into the project then it's less effective as we have to depend on the BPM product. It would be good if everything can be integrated into one as the licensing costs of maintaining all of it is huge. It's well suited for any integration, the variety of connectors and adapters it has makes it easier to integrate with any system.

TIBCO is all around an amazing middleware tool.

Appropriate for hybrid and Cloud integration

It is well suited for moving data from single/multiple destinations to single/multiple other destinations. It is especially well suited when the data is well defined and has an existing schema.

Well suited with enterprise integration with various systems. It might not appropriate for small companies.

Integration Services works well for simple point to point interfaces. It is cloud based with small on-premise agents so requirements are minimal. It is simple to pick up and learn.
If your interfaces only need to talk at polling intervals between Salesforce and on-premise SQL then this is a good choice.
Replication Services work well period. I have yet to see anything else work as well for Salesforce. So I would this is a good choice for this period.
I think the learning curve is low to allow quick startup. The cost is relatively low so easy for smaller companies to justify.
A larger company with more complicated cloud integrations with multiple touchpoints and branched paths will likely find other platforms like Boomi and Mulesoft more suited.

TIBCO BusinessWorks 5 is good for any situation where you need to move a lot of data between different systems. It's fast once deployed and development is fast too. BusinessWorks 6 is still very immature. I wish we would have waited at least another year before getting tangled up with it. I think I've made five necessary upgrades in that time, and I'm currently behind by at least one.

Most suited when different applications built on different platforms need to communicate without much change from their side.

The strong point of TIBCO BusinessWorks is to be a very strong middleware. Useful for integration between heterogeneous systems that need to communicate with each other. It is important to create republication processes through JMS or RV protocols (proposing a protocol of TIBCO). In a scenario where you want to bring processes to the cloud, RV usage is impossible and this is an unfavorable point.

It works well in situations where you don't need instant updates to databases. It works with many different systems.

It is one of the best solutions to build up a really fast middleware that requires handling and process a huge volume of data in a quite short amount of time

When using it to connect Dynamics--which famously does not get a lot of native connectors like some other CRMs I could name--to important third-party systems, it's great. However, the way we are using it--having it managed by said third-party provider--is important, because it is a pretty technical system. No one on my team here has the time to get deep into the technical weeds for perfect setup and configuration, so that kind of support has been vital.

EMS and BW go together nicely

Overall it can bring an application to market easier and quicker than coding something from scratch. With how extensible BW 6.x framework is, there are even more capabilities to perform effective quality assurance when doing development. However, I find it difficult to define and ensure best practices are being achieved.

For straight through processing BW is well suited.

I would use TIBCO in streams where it is important to keep information. Thanks to the use of checkpoints, in case of communication errors (momentary unavailability), you can recover the processes and resume processing without loss of data. TIBCO is also useful in case of database extraction for many records - thanks to the "subset" it is possible to process large amounts of data with simplicity. I would not use TIBCO for simple file transfers (e.g. Connect Direct or SFTP) as plugins for these types of communication often are to be found separately (and at an extra cost).

TIBCO is well recommended for the use towards the big companies where it has integration between more systems.

Tibco BusinessWorks is far more experienced, stable and superior than it's competitor products. The product is very intuitive, easy to develop and design. easy to provide instructions to the team and more. It takes far less man hours to develop a functionality in Tibco BW than to do the same in Java or Pega etc.

Very well suited for ERP, CRM on-premises integration. TIBCO is the champion product.
Less appropriate in APIs, microservices architecture and cloud offerings, integration.

TIBCO is well suited for all complex integrations. The latest version of BusinessWorks is attracting the market.

Well suited for big companies and lots of systems. Too expensive for small companies.

TIBCO BW is very easy to use to communicate with a lot of different applications. [It's well suited] if one company has a lot of different applications which need to communicate with each other. TIBCO BW can easily be a middle man to send messages between different applications. I would suggest TIBCO BW over others.

Well suited for: ESB Integrations with on premise integrations/legacy systems.

Need more work on Cloud platforms like connectors to Azure/AWS systems.