BusinessWorks, BusinessWorks Container Edition, Cloud Integration
I see TIBCO is introducing new pacakages for integration. I see the following three products:
1. TIBCO BusinessWorks 6
2. TIBCO BusinessWorks 6 Container Edition
3. TIBCO Cloud Integration
While I do understand the core difference between TIBCO BW and TIBCO BWCE, I am not clear on the use case of TIBCO Cloud Integration. Can anyone please hightlight the key differences between TIBCO BW CE and Cloud Integration? Also, why was there a need to create a new product like TIBCO BW CE instead of have the native cloud foundry capabilites embedded in BW 6?
0 Comments+ Add a Comment
0 Comments+ Add a Comment
The short answer: TIBCO Cloud Integration (TCI) is less feature-rich, but therefore easier to use. In contrary to BWCE, it uses a Web UI (in addition to TIBCO Business Studio) for development. Besides, TCI runs (only) in the public cloud. The two core use cases for TCI are API Development and Cloud Service Integration.
You use TCI web user interface to define REST APIs (via import or contract-first, based on Swagger 2.0, including generated mocks for testing), define Microflows (for example to configure policies such as throttling), and as interface for service development (with BW6, BWCE or any other framework). TCI is also highly integrated with Mashery for API Management already (though, this is also true for BWCE). The TIBCO Business Studio is still used to implement a REST service.
The 30-day trial of TCI is a great way to understand the differences between TCI and BW6 / BWCE. The included tutorial takes 30 to 60min and shows you all key concepts of TCI: TIBCO Cloud Integration Trial. I really recommend that you try it out (and give feedback if you have questions etc).
Why do different tools exist?
What TIBCO and analysts such as Gartner or Forrester foresee is that most enterprises need more than just one core integration tool (BW6). We already got many inquiries from customers with regards to this. In addition, the different departments and users need different tools to act in a more agile and flexible way. Gartner calls this a Hybrid Integration Platform (HIP).
TIBCO has different integraton offerings:
BW6: Core Integration Platform (On-Premise, for developers)
BWCE: Cloud-Native Integration (On-Premise, Public Cloud or Hybrid, using tools such as CloudFoundry or Docker, for developers)
TCI: Cloud-Native Integration (Cloud-only, not just for developers; the web UI can be used by people who know some technical details, but are no "that experienced developers")
Simplr: Cloud-Native Integration (Cloud-only, for the business user, for simple integration scenarios such as automation of weekly transform-and-copy data from CSV files to Salesforce CRM, Gartner also calls this kind of user a "citizen developer")
Of course, experienced developers can also leverage TCI or Simplr if it is the better choice for a specific use case.
Why not enhance BW6 with cloud-native features instead of creating BWCE?
Several years ago, BW6 was not designed to be cloud-native. Yes, you can deploy BW6 applications e.g. in a Docker container. But as BW6 is not designed / built for that, it is not easy to "change it" so that it offers all the features you need for cloud-native microservices architectures. Therefore, creating BWCE was the most reasonable option. Microservices and Docker et al got a massive traction last 18 months, and TIBCO could act quickly to offer a great tool to leverage microservices and containers - if wanted.
Do I have to create my application three times (BW6, BWCE, TCI)?
No. The good news is that you can use all your implemented services in all three runtimes - as long as you only use the features, which are supported. For example, BWCE services running on Cloud Foundry does not support files (because Cloud Foundry does not support this). Thus, you cannot use the File activity in the BW Business Studio.
What about this "cloud-native", "microservices" and "containers" you mentioned all the time?
Microservices, containers and a cloud-native architecture are the key concepts you need to know to understand why BWCE is TIBCO's tool for the (private or public) cloud instead of BW6. Today - what a coincidence :-) - my newest article was published: Microservices, Containers and Cloud-Native Architectures for Middleware. It explains all these concepts in much more details.
Hope this helps.
Hi, I am just getting started on BW6-CE. Based on the following point mentioned above:
"Several years ago, BW6 was not designed to be cloud-native. Yes, you can deploy BW6 applications e.g. in a Docker container. But as BW6 is not designed / built for that, it is not easy to "change it" so that it offers all the features you need for cloud-native microservices architectures. Therefore, creating BWCE was the most reasonable option."
even on a private cloud, the recommended product would be BW-CE.
The BW-CIP is not for private cloud - it is a Tibco hosted public cloud product. ("Besides, TCI runs (only) in the public cloud.")
Yes, BW6 is compatible and supported with public and private cloud (note that you have to choose FTL under the hood for messaging instead of In-Memory or EMS).
Which product should you choose? Basically, it depends if you want to run on containers (Docker, Kubernetes, OpenShift, CloudFoundry, etc) or not. If so, then BWCE is the right product. If not, then BW6 is the right product.
Most customers choose BWCE for cloud deployments due to the benefits of containerized deployments.
"BW6: Core Integration Platform (On-Premise, for developers)" is this product compatible with cloud, public or private?
On a private cloud which BusinessWorks version should I choose?
Thanks for the explanation Kai