Why TIBCO Businessworks as an ESB through your organization
August 24, 2017
Why TIBCO Businessworks as an ESB through your organization
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with TIBCO BusinessWorks
We use TIBCO BusinessWorks as an ESB middleware solution across the whole company. Every integration between applications (generally external but sometimes internal) is implemented in TIBCO Businessworks.
The main solutions we've implemented are:
The main solutions we've implemented are:
- System integration between a new web platform (Salesforce e-commerce cloud) and our legacy backend systems (AS/400 and Teradata, mainly)
- Adoption of a new third party logistic provider in order to deliver all of our e-commerce orders
- Real time Stock and Sales systems, which allows us to give users the information of real-time stock at our stores and give our directors real-time sales information
- Working with XML files is awesome, really easy and useful. Reading, validating, parsing and hard transformations are really difficult to implemente in other techonlogies.
- Message management. EMS integration is great, provides fault tolerance, scalation, high volume control, etc.
- Routing. Making decisions at real time on which target systems must receive a message.
- Memory consumption. Production servers requiere high volume of logical memory available.
- IDE in 5.x version was very stable but "old-fashioned". Eclipse-based IDE in 6.x provides lots of advantages (such as Java integration) but development experience has become much worse: less stability and migration from 5.x is imposible.
- Very Positive: e-commerce system (customer integration, online orders, etc.) has been incredibly improved. Now we have a real-time integration and the system is stable, robust.
- Less people is needed in order to maintain/operate integration systems, we need less inversion in external expertise.
- Time to market is very little, we implement new integration flows quite fast.
- Building new flow integrations and reusing them with new channels (clients) or backend systems is really fast. Note: we've implemented an Architecture Framework in TIBCO Businessworks on which we build our business processes.
- Lifecycle deployment is also fast using AppManage through Jenkins. However, stability can be improved since the process sometimes crashes.
- Any bug is fast implemented, tested and deployed at production environment.
TIBCO BusinessWorks is the best solution for this purpose. Other solutions (like the one form IBM) is much more complex at development phase and has less tools. TIBCO is really intuitive at development phase providing lots of tools and making it easy to configure them. Although IT knoledgement is recommended it's not a must, so any techinical skilled person can be productive.
In 5.x version this is not as good as expected. In 5.x IDE is not Java integrated so no jUnit or other frameworks can be used. Thus, all unit/performance/load/etc. testing must be impemented ad-hoc and/or using externak tools (such us jMeter or SOAP-UI for jms/rest testing). I know version 6.x improves this, but all legacy flow integration developments in 5.x can't be easily migrated and as mentioned before development experience is worse.
TIBCO BusinessWorks offers more options and better development experience. Performance and operating applications is also better.