What is our primary use case?
We use this solution for:
- Enterprise Service Bus
- Enterprise Application Integration
- Application to Application Integration
- Business to Business Integration
- Cloud Integration
- Service-Oriented Architecture
- SOAP web services
- JMS messaging
- Adapters (SAP, ADB, File, etc.) related implementations and integrations
How has it helped my organization?
This is a user-friendly product stack and provides you with a reliable, robust, and high-performance Integration solution. If the solution is designed and implemented well, there are minimal chances of integration failures due to ESB. Developing interfaces with Tibco BW is fairly easy and straightforward. Monitoring using Tibco Hawk and MAR features are also effective.
What is most valuable?
The most valuable features are the monitoring, ease of use, and easy to understand development GUI.
It is a straightforward installation and creating an environment is easy.
The interfaces are stable and reliable. Tibco EMS is one of the most reliable and robust messaging products in the market.
There are a lot of options to enable high-security needs.
This solution needs low maintenance and has highly efficient ways to address planed downtimes such as patching activities, has zero integration downtime, and avoids any adverse effects on Interfaces.
What needs improvement?
The transparency, complexity, and stability of some products, such as Tibco BC, need to be improved.
Migration from BW 5.x to 6.x still has issues. Migration to cloud solutions or products should be made convenient, transparent, and easily understandable.
Improvements can be made in the product support area. At times, effective and accurate solutions were not provided.
For how long have I used the solution?
We have been using this solution for twelve years.
What do I think about the stability of the solution?
This solution is one of the most stable in its league. Lots of customers have switched to the Tibco stack because of stability. Good designing, architecting, guidelines and standards play a large role in having a stable and robust Integration environment.
What do I think about the scalability of the solution?
This solution is highly scalable both ways (Scale Up or Out), especially now that the container and cloud edition gives a tremendous edge from a scalability standpoint
How are customer service and technical support?
There is definitely some scope of improvement needed in the vendor/technical support area.
Which solution did I use previously and why did I switch?
There have been customers which have moved from other products to Tibco stack, because of stability and performance issues.
How was the initial setup?
This solution has a fairly straightforward initial setup.
What about the implementation team?
We integrated this solution with support from the vendor team.
What was our ROI?
Our ROI for this solution is good.
What's my experience with pricing, setup cost, and licensing?
The licensing cost is a challenge for quite a few customers.
Tibco Products may have a high initial setup cost in terms of pricing and licensing. However, it depends on what agreements are made with the Tibco vendor, what kind of setup is being done, and how efficiently the architecture is laid out.
What other advice do I have?
Featurewise, overall, the Tibco product stack addresses most needs.