BW Man

Tibco Business Work is used to build integration layers based on SOA principles.

Main scenario: Integrate internal source systems based on different technologies with SAP C4C CRM. An event based architecture was built using an In-Only pattern based on XML over JMS. Soap over http services exposed by SAP were easily consumed using the out of the box functionality of the product.
The integration layer was built defining a Canonical Data Model to reduce the number of transformations and simplify the code maintenance.

Using TCI there is no effort related to Environments setup, runtime is completely managed by the platform and there is no operational effort required. Software upgrade, usually a time consuming activity, is automatically managed. Messaging is built-in in the platform providing a great developer experience. Easy integration with Mashery APi Management.

I used TIBCO’s cloud based solutions as new deployment platform for customer having their first experience with Tibco and/or for customers trying to enrich their runtime architecture. Customers quickly understand the power to deliver products in weeks (or days) compared to months required with other tools or with On Premises setup. TCI simplify the Cloudpath for customers who wants to move from their BW6 On Premises infrastructure to an IPaas solution. Most of the applications, if properly designed, can be moved to TCI directly.

Tibco BW6 applications are easy to migrate if the application design was service oriented. More effort is required if the applications are file-based. The main effort can be related to applications using messaging, if the idea is to move away from On Premise setup and use Tibco Cloud Messaging. In some cases an hybrid architecture can be a better solution.

Tibco new capabilities have to be evaluated to understand if they can be immediately used. Tibco messaging portfolio enriched with new products, like EMS and Kafka, are for sure something every organizations need, but an analysis is required to understand if the realeased version has some limitation compared to the On Premises version. Sometimes this is a time consuming operation, requiring prototyping. Feature like Cloud Mesh when introduced, in my experience, was not simple to use, due to some limitations-

Tibco give a great support during the migration of the Environments to another region, required to have the BW applications deployed closely to the region where Tibco Mashery was deployed.

Feedback is usually taken in considerations. In case of bugs/issue related to the products/new feature you are always supported in the best way with a workaround or other solutions. In case is not a bus, and the limitation is related to a particular use case, maybe it takes more time, and an enhancemetn request is created.

On AWS

I havent used these tools

Top 3 features :
- Deploy directly from Business Studio with few click
- Out of the box integration to expose private endpoints only with Tibco Mashery
- Scaling directly from the UI

Best feature is to make BW endpoints private and expose them using MAshery to increase security

Best features are private endpoint, and the messaging integration.
There is still some limitation but Messaging provide out of the box many solutions. In Cloud world is a point to consider.

Not Sure