TIBCO ActiveMatrix Service Bus Reviews

The primary use case of this solution is to provide our customers with a faster way to get their data and to connect information between different environments, especially with corporate companies that have different branches in different parts of the country. They need to receive and share information as quickly as possible between the different environments.

This is the main way that we identify, in a fast way, to connect with different platforms.

It's a platform of interconnectivity that we provide to our clients with this solution.

We are specialized in installation and deployment using this platform. We use it to move the transformation of the companies to the new mature service-oriented architecture. 

TIBCO has the best platform in terms of speed and ease of use.

The brand is very important, it has a percentage of the research and development of the product. They look at how you can get to obtain the best features from the platform. Most other platforms offer the same features in the same way and the same kind of platform, but with TIBCO, you get answers in milliseconds.

If you have high traffic transaction volume and you need more speed, more governance in your services, then you need to use TIBCO. This is the value that TIBCO offers and how it differs from others.

One of the areas that this solution could be improved is to provide the vendors with updated information. We don't always know what is going on with the development of the solution.

In the next release, there should be improvements made to the API manager. Other platforms are better.

This solution is stable.

This solution is scalable.

I don't work directly with technical support, but my team does. To my knowledge, they have not had any issues with technical support.

The technical support is good and they are knowledgable.

The initial setup is complex. Not all companies are ready to move forward with this platform because they don't understand how it works, what the real benefits are, and how to take advantage of this platform to obtain the best results for your company.

Before we can begin, we must understand the vision of the business. When you have that understanding then the setup is easy, but if you don't then it's complex.

It depends on the company, but it can take approximately six months to deploy this solution.

We consider the preparation of the environment, the installation, the testing, then the training. Not user training, but training the technical team in the companies to manage the platform inside the environment. 

Then we deploy the solution together. We apply one life cycle, then certify it by CMMI.

Part of the sales process includes deployment and implementation. If this solution is not implemented correctly it is not the fault of the solution but with the vendor and not providing the necessary training.

With this platform, the return of investment would be less than one year.

There are many ways to measure the return of investment, it is not always just about how much money they will make, there are other factors.

ROI can be measured in terms of effort, social benefits, political initiatives, and many other things.

• If you reduce the social impact you can save money.
• If you reduce the way that people work or the way the citizens work with the government, you will save money.
• When you control things, there are benefits to that.

We consult with TIBCO to understand the market and try to get the customer's different levels of pricing.

Latin America has many vendors working with the same type of solutions that are open source.

Companies feel that by it being open source it could be the key to getting a free platform, but that is not the case. They would prefer to purchase a solution like TIBCO but don't have the budget.

In Latin America, there is a lot of immature environments in terms of connectivity or service-oriented architecture.

The wave of technology or the wave of the transformation came from the US and other first-rate countries. Latin Americans adopted technologies. It's not easy to deploy this type of technology quickly.

The first challenge is with the consultant and in making the sale by explaining what exactly is the value that you would be getting by staying in a real service-oriented architectural environment.

The second is that the corporate companies grow in a Catharsis because the growth of the companies is not well planned.

The best way to fix the problem that they have is to buy a platform to connect all of the different platforms that they have acquired in the past.

It's not enough to purchase the right product. You have to hire the right team to help you deploy this solution. Most of the vendors forget the customer, but the most important thing is to have the customer understand the solution that they will be working with.

The founder of TIBCO is an entrepreneur who always invests money to improve the product. He invests money to improve most of the products that he has. You will always be a leader in this area if you don't lose the philosophy of investing to improve.

I would rate this solution a ten out of ten.

We primarily use the solution as a middleware for exposing APIs so that one app can talk to another in separate application via APIs. 

There are so many valuable features on the solution, there's almost too many to list.

If TIBCO could be able to sort the size of their base image in the Container edition, it would be really marvelous. Right now it's around 299 MB. We'd really want it to reduce to a few MBs.

TIBCO needs to improve its monitoring capability to be able to make use of alerts and to be able to have an alert threshold. For example, if there is an API, if it encounters a given number of errors or long response times, it could send an alert to a configured list of users either via email or SMS.

The solution needs to have cloud integration. There should be continuous integration and continuous deployment of new features.

We've been using the solution for six years.

The solution is very stable.

I believe the solution is scalable. With the Container edition, even with the non-containerized edition, depending on your architecture, and how you write your code, it's very scalable.

Currently, we have about 10 users as a support team. TIBCO is an integration layer, not really a place where users can log on and do transactions or approvals. It's not the type of technology that has a large user base.

We do plan to increase usage in the future. There are so many new integration use cases that we want to use on TIBCO. 

The technical support offered by TIBCO is perfect. I don't think we have faced any issues when dealing with TIBCO support. Each time we raise a ticket and put the correct classification, they normally respond by SMS. We've been satisfied with the level of support we've received.

In the past, we tried using Oracle OSB. I don't think we'll go back and use them again. TIBCO has proven to be far superior. We didn't switch to TIBCO. What we wanted to do is to explore what Oracle had to offer. We later realized that the capabilities that TIBCO had were far, far superior to what Oracle was able to offer so we chose TIBCO instead.

The initial setup was very straightforward. There was no complexity in the implementation. Deployment takes a maximum of one to two weeks.

The last time we implemented the solution, we were installing certain components and adding in hot fixes.

We're users as well as consultants of the product.

Although we currently use the on-premises deployment model, right now, we are also exploring the possibility of having the service deployed in some hybrid form of the cloud. That's still on a theoretical basis. Nothing substantive has been done yet.

I would recommend the solution to any other organization which is interested in standardizing their integration layer. To me, this solution has really served the requirements we had with respect to enterprise integration.

I'd rate the solution nine out of ten.

There are a number of applications including use cases from the health industry, including health human services. 

We're making good use of it, although our version is an outdated platform that needs to be replaced in order to be ready for the future. For example, we will be moving applications to micro-services and migrating components to the cloud.

The most valuable feature is that it is a service-oriented architecture, SOA-based.

Our version does not have cloud capabilities.

Containerization is not supported.

The is no support for Agile development.

We have been using this product for 12 years.

This product is very stable.

Scalability is fine, although our current version is just not able to move us to the future.

I was not part of the original implementation, although I'm sure that it was complex.

We have been working with this version of TIBCO for at least the past 12 years. We are now looking at replacing it with either a new version or a new solution from a different vendor.

This is a good platform but in our case, it needs to be updated. The future is on the cloud, the future is containerized, the future is Agile development, and our version is incapable of any of this. 

I would rate this solution a nine out of ten.

Our primary use case for this solution is to provide a BPM for our customers.

We have been working a lot on TIBCO products, including this solution. We have a team of thirty to forty people working exclusively on TIBCO and have a dedicated unit with revenue targets set specifically for this.

This solution, as well as other products from TIBCO, are helping us grow.

The most valuable feature is its flexibility, where it allows the users to create workflows. In terms of scalability and performance, it is also very good.

In the configuration, where we need to customize, it takes more time that we expect it to, ideally. We have found workarounds for some of the issues, and we have given feedback on these things directly to TIBCO.

The integration can be more user-friendly.

The stability of this solution is excellent. I would give it nine out of ten.

The scalability is very good. That is one of the strongest points of TIBCO and I'm quite satisfied with the scalability.

We have approximately fifteen customers, but of course, that would mean many more users. We focus on TIBCO, but there is a lot of competition from the other product vendors. This makes it a challenge to increase our usage of this solution. That said, we have plans to reach out to a lot more new customers.

As TIBCO releases products or a new version of a product, we start using them as we go around to some of the customers that we are involved with.

The technical support for this solution is very good. Whenever we are stuck with any kind of technical issue, we reach out to TIBCO and get very good technical support from them.

The TIBCO solution is not the only one that has been used in my organization, but this is the only one that I have worked on personally.

The initial setup is literally straightforward and we did not have too many issues with it.

The typical implementation strategy depends on the volume of the business, the number of transactions, and the size of the customer. Typically it takes six to eight months for us to complete an end-to-end implementation cycle for a medium to large sized customer.

In the typical deployment team, we need ten to twelve people for each customer. Some of the staff are developers, but you need a core architect. It is the role of the architect to visualize the solution and create the architecture. Once we have the architect and a couple of leads, the rest are the developers who can do the actual implementation. You also need an administrator, so there are four different roles involved in the implementation.

We are the ones who handle the integration of this product, and we don't normally have to depend on anybody else. Sometimes, TIBCO themselves will assist us, but otherwise, we do it ourselves and don't usually have any issues.

I would consider all of the revenue that we get from TIBCO to be ROI. We do invest resources to get them trained on various TIBCO products. At the end of the day, we are using them to implement solutions for different customers, and we get that revenue. It is approximately three to four million per year.

When it comes to cost, TIBCO is much more competitive than a product like Pega.

Our licensing cost is in the area of half a million, annually. There are no costs in addition to the standard licensing fees.

From a BPM perspective, we did evaluate other products. Part of our evaluation included the figures for pricing, and other solutions are a lot more expensive. This is one of the reasons that our customers are reluctant to go with Pega. 

My advice is to evaluate all of the competing products, which is something that we can help with. There should always be a good rationale behind the choice for a particular product.

I would rate this solution an eight out of ten.