Tibco BW process, a good combination with EMS (JMS)
Updated November 22, 2017
Tibco BW process, a good combination with EMS (JMS)
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with TIBCO BusinessWorks
BW Processes, in conjunction with EMS (Enterprise Messaging Service) are the critical components of our ESB application through the Federal Agency we are supporting.
- BW uses its own JVM container, which is highly scalable and portable
- BW is very configurable and high performing
- BW is very analogous to the microservice implementation concept and smaller in foot print than the typical J2EE app server containers
- Startup time when instrumented with JVM monitoring software
- XML-based configuration is great for separation of logic with TRA run time, but the parsing and traversing could be time consuming.
- In-person training
Training available via Tibco, not open source.
- COTS product, reliable, superior support from Tibco support and PSG (Tibco Professional Service Group)
- Good investment with mission critical enterprise infrastructure and apps
- Could be pricy in licensing and maintenance cost
BW CE offers good cloud native integration capability with containers, thus renders it more suitable for the migration towards microservice architecture.
Visual based mapping through Designer is a good tool for developers. It makes data mapping detached from the underlying parser code, which saves development time and effort.
Designer offers pretty robust testing capability. But the real industrial level functional and integration testing still needs to go through the typical QA process through lower to upper environment. It will be nice to have more out-of-the-box with JUnit, SOAP UI and JMeter testing to simplify the CI-CD process
Tibco BW is uses its own JVM container to implement java-based multi-threaded application server. It could be implemented in a smaller footprint, microservice-like as well as monolithic way with traditional SOA artifacts. It is robust and high performing.