TIBCO BusinessWorks Reviews

We are using the solution to control different markets, banking, security, and transportation. The solution can be deployed both on-premises and cloud.

The most valuable feature is the integration.

The cost has room for improvement.

I have been using the solution for almost 20 years.

The solution is stable.

In most cases the solution is scalable but it depends on the environment.

The technical support is good but it depends on which region we are dealing with because they have support in India and the USA.

Positive

The initial setup depends on the complexity of the organization.

The license is based on the subscription model. The cost depends on the components required.

I give the solution a nine out of ten.

Depending on the size of the organization we need between one to 50 people for maintenance.

I recommend the solution to others.

We using TIBCO BusinessWorks 5 and the container edition to work with integrations.  

It is a cloud product. The most valuable part of the solution is the ease-of-use and deployment.  

I think TIBCO needs to do a lot in terms of making it a first-class cloud solution. Because the issues that we are facing have to do with the container-based image. It is so big that it makes it very difficult to autoscale.  

They need to do a few things. First, they need to make it smaller, and also to make it really a true cloud citizen. Because if you compare with other solutions, TIBCO is playing catch up in terms of cloud adoption.  

I just received a new version the other day and they have included quite a lot of changes. It is impossible to tell what they have already taken care of. But I have experienced that there are some security vulnerabilities that they need to fix on the Docker image. I do not have the specific details because we have not totally isolated the problem, but there are some vulnerabilities and those are apparent in the TIBCO container edition.  

I have been using TIBCO (The Information Bus Company) Businessworks for the last seven years.  

I think TIBCO is relatively stable. There is not much downtime.  

With TIBCO as a platform, scalability should not be an issue because it is cloud-based and should support autoscaling. You run the Docker image on Kubernetes or RedHat, then the BW (BusinessWorks) site is always relatively stable and also very easy to scale. It is scalable both vertically and horizontally.  

As far as looking at it as scaling to a larger number of users, TIBCO is really not a GUI where a user will log in and perform tasks. It is middleware, where you use it to expose APIs and from there you have systems connecting to it. So it supports the operations of the entire enterprise. You can not really quantify the number of users because it is just a tool for exposing APIs.  

I work with TIBCO technical support almost every week. We often have to raise a ticket. Not in a bad way. Most of the time it is just that we come to a new situation or requirement and it is better and quicker to have them assist us. It is not because of the stability of the solution. It is always a new challenge where we require their technical assistance.  

The technical support team is usually very prompt. I think the kind of support we get from TIBCO is unparalleled.  

There was a time we did a pilot with Oracle SOA (Service-Oriented Architecture). But in terms of a faster API tool, TIBCO is miles ahead of SOA in terms of functionality and setup. It is also better in terms of ease-of-use. Oracle is too complex. I find it unnecessarily complex and heavy.  

I think the setups that I have done were mostly straightforward. They really did not require a lot of back and forth or complicated configurations. But in some scenarios, I have had complicated implementations. These are businesses with complex business requirements and that is when I need to contact the support at TIBCO.  

The initial setup normally takes between a week to two weeks. This is for the deployment and then after that, we spend a little time doing some testing. It is really not an outrageous amount of time for deployment at all.   

The only caveat I would tell people considering this solution is that there are issues with the container-based image. It needs to be made much smaller. But as a tool to help you work doing what it was made to do, it is a very good product.  

On the scale from one to ten where one is the worst and ten is the best, I would you rate TIBCO as a nine-out-of-ten. If you see the amount of work that we do with it and the kind of revenue and customer experience because of the value that we get from TIBCO, the high rating is warranted.  

We use the solution to develop applications. 

I would like the solution to be integrated into the cloud. 

I have been working with the product for 10 years. 

I would rate the product's scalability a nine out of ten.

I would rate the product's scalability a seven out of ten. We can change things as per requirements. 

The solution's support is helpful and the response time is good. 

The tool's installation process is easy. 

I would rate the solution's pricing a three out of ten. 

I would rate the solution an eight out of ten. The solution is mostly for enterprise companies. The product is reliable and stable. At the designing level, developers can use low code. 

We primarily use the solution for various systems.

The reliability is the most valuable aspect of the solution.

One of the main handicaps on version 5 was its development environment. In comparison with other Eclipse-based products, it is not the easiest landing at the first stages of learning. For advanced developers, it results in a simple and direct environment. It also does not facilitate integration with other external tools (release management etc). All these issues are fixed on 6 versions, but we have not migrated at this time.

Pricing is not one of its strengths. Using Tibco BusinessWorks implies adopting a non-trivial set of products (Hawk, Rendez-vous, EMS in most cases), and previous cost models enabled scalability on installation and deployment. I think that current commercial management on the company is betting on promoting a strict model of licensing per product and instance that makes pricing a disadvantage in comparison with other platforms.

Another gap fixed on new releases is cloud approach. We are investing in cloud migration, and currently, all our installation of this product is on-premise. Tibco BW 6 lets you choose on-premise or cloud (Container Edition) deployment. I cannot evaluate it at this time, but this was a gap on the previous version.

The solution is stable. We haven't had any serious technical issues.

The solution is scalable. We have 20 or 30 people on the solution and a team that handles deployment and maintenance.

Technical support is good.

We didn't previously use a different solution before implementing TIBCO.

The initial setup of the solution is easy. Deployment times vary. If you are setting up a straightforward deployment, you can do it in a few hours. If it's more complex, it could take a few months. 

We handled the implementation ourselves.

Our investment is justified based on systems maintenance and migration. This product is our business backbone, so it must be flexible, reliable, and expose a low latency. It's not easy to calculate an ROI by itself, but on the whole of deployed projects.

We use the on-premises deployment model.

I would recommend the solution to others.

I would rate it eight out of ten. It's very reliable, but it's not fast when it comes to adopting new architecture. It's also slow when it comes to introducing product improvements. 

TIBCO BusinessWorks is mainly used to build services based on SOA principles.

It can be used to build synchronous services using SOAP or REST, event-based architecture based on XML over JMS.

REST services based on Swagger Specifications are supported.

BusinessWorks reduces development time, helping developers to focus on business logic. The Business Studio interface based on SCA Standards helps to show the business logic at first look and improve code maintenance.

Runtime entities management is very simple.

Web service development is very simple. It is a service built very quickly, so you can focus on performance and error handling. XML to JSON transformations, out-of-the-box, helps to build REST services.

The OSGI console is available to debug different issues and get low level informations on the applications development, like bundle, dependencies, etc.

Improve Business Studio's stability to further minimize development time.

A possible improvement could be to give the capability to use different profiles for each AppNode when an application is deployed on an AppSpace.

No issues.

Runtime entities (like AppNodes) can be added on the fly, and applications on the same AppSpace are automatically deployed on the new AppNode.

Customer support is very efficient.

I have not used other solutions.

It is straightforward.

Not my area of expertise.

Our primary use for the solution is contrariwise integration.

Support is the most valuable feature of the solution.

The solution needs integration support.

Currently, it's all very technical and developer-driven. There is no support for a non-technical user to define the integration process. If there was support for integration for them, it would help them define the integration themselves.

More monitoring would also be useful in future releases.

The current version is stable, but now it's got no support for the newest version.

The solution is very scalable. It can handle a lot. We have encryption plus integration servers running on that platform currently.

Technical support is average. It's not the best.

I've personally used a different solution previously. TIBCO was basically a client requirement. I've implemented multiple integration platforms according to the client's requirements and preferences.

Deployment took over a year. We have about four people that handle maintenance.

Users are only charged a yearly maintenance cost. I'm not sure of the exact amount, but I know it's quite expensive as a solution.

We are using the on-premises deployment model.

In terms of advice, I would suggest anyone hoping to implement the solution do their market research first. There are other products available which are easy to implement as well. Do your research and then choose the best product according to your needs.

I would rate this solution six out of ten.

We are a system integrator and this is one of the products that we implement for our clients.

We are using this in the banking industry and we have some APIs that are based on BusinessWorks.

The most important thing is that it is easy for developers to work with.

BusinessWorks is robust, flexible, and scalable.

The cost of this product is too expensive for smaller companies or those with a small number of integrations.

There should be more support for cloud-based integration.

I have been using TIBCO BusinessWorks for more than five years.

This solution is very much stable and we plan to continue using it in the future.

This is a scalable product and we have about 200 people who use it.

The support is wonderful and they respond on time.

Within the past year, I've explored MuleSoft. I haven't used it much but I know how it works. It has different advantages, and it's more API-based. It's a cloud-based solution.

The initial setup is very straightforward and it will not take more than a few minutes.

I deployed it myself. We have a 10 member deployment team that follows a sprint cycle. They include DevOps people, administrators, and others.

My understanding is that the licensing is very costly.

For enterprise integration, this is definitely a very fitting product. I am talking about an organization that has a large number of integrations. However, for cases where there is a low number, this is definitely not a good choice because of the cost. I don't think that it's a good fit for the small customer.

The vendor has also come up with a cloud-based integration, which I think will ultimately be good but to my knowledge, at this time it hasn't picked up well yet. 

I would rate this solution and eight out of ten.