It is basically for managing data and specifically master data for clients, such as big corporations who have multiple millions of data, including clients, products, etc.
The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.
Use our online form to submit your review. It's quick and you can post anonymously.
It is basically for managing data and specifically master data for clients, such as big corporations who have multiple millions of data, including clients, products, etc.
The best features of the TIBCO EBX solution would be ensuring data quality by using Match/Merge add-ons. It has multiple add-ons to search for data in TIBCO EBX. It is pretty performant. Matching the new data inserted on the software is done in a timely manner and it is pretty efficient. It is easy to work with as a developer as well. It is easy to code, especially because it is coded in Java. It is pretty clear in terms of documentation and how to use it. It might be a little bit complicated, but when you get used to it, it gets easier and easier.
Good data modeling would help. Maintaining a purging process for unused data or closed data spaces is important because we can take a copy on a data space and work on it and then merge it or not. If we are testing, we do not merge. Purging those unused data spaces would be good for performance and for leaving some space in the database as well. That could enhance performance.
It has an indexing mechanism that indexes because you have the database on a server and you have the application in another server. What TIBCO EBX does is it has an index. It indexes the data on the current server, on the application server. This can enhance the performance in terms of searching, altering the data, and accessing the data. It is pretty quick, thanks to the indexing, because it does not have to go to the database server in each consultation of the data. It can point to the index and get the data.
Some optimization on the database and how it is handled would be beneficial. Currently, we have a lot of data that takes up significant space on the database server. Some optimization in that regard would be a plus to the software as a whole.
Some enhancements could be made in terms of how the documentation is structured. Sometimes we struggle to find explanations for some features in the documentation. If they can work on that, it would be great. Overall, I think it is good.
I have been working with the TIBCO EBX solution for five years now.
It is a little bit complex. Setting up is probably one of the hardest tasks to work on with TIBCO EBX. It is not extremely complicated, but it is understandable in terms of the volume of the data they can manage. It has to have its own server, database server, etc. You have to work with Tomcat to set that up and data models in the first step. After that, the customization depends on the needs, but it is more or less easy.
I think it is pretty stable. It does not have many bugs, and if we have a bug, the display of the error is quite straightforward. Sometimes we get some issues, but we figure out later that the issue was something we did not set up correctly. In terms of production deployments, we did not have many issues. It is pretty stable. We do not have bugs in production. Sometimes out of nowhere you get something, but with TIBCO EBX it is quite stable.
It is pretty scalable. With my current clients, we have over 150 million records managed by TIBCO EBX and it is pretty stable, even with a huge database. We are working with the editor to find a way to make that shrink through optimization. They promised that within the next releases, they would find some solution to that. My only concern is the actual database and its volume. That is the only thing in terms of scalability. Otherwise, in terms of performance, consultation of data, and APIs, it is still pretty stable even with the huge amount of data.
They are pretty helpful. They have a policy where each client has a reference that you can call and reach out to if you have any issues. They also have an online platform to submit cases if we have any issues to the support. In terms of response time, it is pretty reasonable. It does not go beyond four hours or something similar. They get back to you quickly.
Positive
I am new in MDM. Since I got out from the university, I started with TIBCO EBX and it stayed that way.
Setting up can be a little bit complicated, but once we get through that, it is a pretty straightforward and stable software.
I did a training with them which was paid by my company. In terms of business, personally, I do not have any business with them.
I know there is Informatica and Semarchy. I am not quite sure if Salesforce does the same thing, but it can do that as well. I have not worked on any of them.
It provides significant time savings and helps with data management, particularly in how data is matched between other data to prevent duplicates. You can do matching with millions of records pretty quickly. That could save data and you can do it in real time as well. Through the indexing, we can access data quickly.
It is pretty integrable. With my clients, we have integrated it with multiple systems that gather data from external sources or internal sources. We can connect with APIs, REST API or SOAP APIs. It can get integrated and connected with other systems. It is a little bit complicated, but it gets the job done.
Good data modeling helps, and maintaining a purging process for unused data or closed data spaces is important. TIBCO EBX has an indexing mechanism that enhances performance in terms of searching, altering data, and accessing data.
Based on my current client and client feedbacks, I would rate TIBCO EBX an eight out of ten.
Currently, we are using TIBCO EBX for MDM purposes. We get data from different sources and perform sanity checks on this data. Then we store and publish the data.
The features of TIBCO EBX are highly customizable, which is something I appreciated. We can customize every part of it. We can set where the labels appear, how they appear, and their order. We have all of these capabilities readily available.
We can implement rules, regulations, and constraints that are highly customizable. Everything is in Java, which could be considered a drawback. Currently, they are implementing some normal use-on-the-go rules, but most functionality remains in Java.
TIBCO EBX really helps because not everyone uses the same structure. Some use similar models, while others use different ones or might need changes in the future. We can have any sort of data model, any kind of data structure, table format, and we can reuse them. For instance, instead of a single country field, some might need multiple variables such as primary country and secondary country.
We can import data directly from files. If not, we can use SQL views or queries for importing. These are the main integration capabilities in TIBCO EBX.
The workflow functionality is excellent in TIBCO EBX, including the UI. In workflow, we can have multiple steps and implement rules and regulations within the workflow itself. If something is incorrect, specific actions can be triggered. This helps data stewards by implementing sanity checks that can throw errors or redirect the flow, preventing incorrect data from being populated.
The UI has improved, and while the matching scenario still has some challenges, it performs better than before.
TIBCO EBX can be challenging to handle due to its customizability. While it is good to use, it is not particularly easy to use. We still somewhat struggle to implement new features or use something on the go, though things are improving gradually.
TIBCO EBX has performance issues, particularly with speed. Replicating data can take several hours even with normal median data. When multiple users are accessing data and if a particular table contains more than 15 million records, the system struggles. These issues might be resolved by increasing RAM or improving performance, but there is still room for improvement. It was worse in version 5.9, but version 6 shows some improvement.
Previously, there was a relational model in data spaces directly connected to TIBCO EBX and the UI. Now that has been removed and replaced with a semantic model where everything is encrypted by TIBCO EBX by default. For replication, we need to use an additional module.
However, they are making positive changes regarding permissions and the UI has significantly improved compared to previous versions. They have announced plans to introduce new features such as parallel import and parallel jobs.
I have been working with TIBCO EBX for four years.
The initial setup of TIBCO EBX presents challenges when there are multiple modules that need to be transferred between environments. There is no straightforward method for transferring permissions and configurations. We need to use staging modules for this purpose. While this setup process can be time-consuming, it is typically a one-time task per environment.
TIBCO EBX is stable, though there are occasional bugs. When these are reported to the company, they work on resolving them and release new versions.
TIBCO EBX requires additional RAM for scaling, and performance can be slower when scaling up.
I would rate the technical support and customer service of TIBCO EBX 3.5 or 4 out of 5.
Positive
We have been using TIBCO EBX from the beginning, starting with version 5.9 before upgrading to version 6.
The initial setup of TIBCO EBX presents challenges when there are multiple modules that need to be transferred between environments. There is no straightforward method for transferring permissions and configurations. We need to use staging modules for this purpose. While this setup process can be time-consuming, it is typically a one-time task per environment.
I cannot provide a proper comparison as I am not familiar with other products.
TIBCO EBX can be challenging to handle due to its customizability. While it is good to use, it is not particularly easy to use. We still somewhat struggle to implement new features or use something on the go, though things are improving gradually.
I am working with the on-premises version of TIBCO EBX. While I am not familiar with the exact pricing, I know that TIBCO EBX is positioned in the higher end of the market.
I would recommend TIBCO EBX for organizations that require extensive data customizations. However, if the data structure is simple without complex requirements, TIBCO EBX might not provide significant additional value.
On a scale of 1-10, I rate TIBCO EBX an 8.
