BW from prem to cloud
Updated November 27, 2018
BW from prem to cloud
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with TIBCO BusinessWorks
BusinessWorks is a must for every integration scenario. Being cloud native makes it ideal for on-premises (Business Works 6), on cloud (TIBCO Cloud Integration) or hybrid architectures (Business Works Container Edition).
- API Implementation
- Seamless XML/JSON mappings
- Large set of connectors
- It would be great to have application templates to further speed-up prototyping and standardized developments
- Online training
- In-person training
- Self-taught
A good kick-off, but not crucial to the make the difference. Most of the skills were gained by interacting with experts
- Implementation times reduced
- Improved business view into process flows
Definitively much faster development than main competitors.
Real first class mapping tools, completely visual. Moreover, whenever you need to go that last mile you can also manually edit the mapping as an XSLT
Testing goes from internal testing via JUnit, not endpoint testing via JMeter or SOAPUI. But don’t forget that you may not need any of those. BW6 provides an automatic testing facility via swagger.io.
- osb
Definitively more modern, capable and complete
Innovation, Integration and Support
- migrating a legacy java application to a microservice architecture, by embedding old java functions
- containered microservices
- Databases (oracle, db2, mysql)
- Mainframe (via MQ)
- Mobile Apps
- Web Portals
- Custom Applications via unusual TCP protocols
very high quality integrations, especially if XML based, and not very difficult to achieve
TIBCO BusinessWorks Support
Pros | Cons |
---|---|
Good followup Knowledgeable team Problems get solved Kept well informed Immediate help available Quick Initial Response | None |
Yes - it was resolved, but in about a year time
there were performance issues due to one version of BW, and we interacted strongly with Support and Engineering to have an Engineering Build fixing these performance issues, which we finally did