MDM Tibco EBX Consultant at a insurance company with 51-200 employees
Consultant
Top 20
Jul 16, 2025
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.
Associate Director at a financial services firm with 10,001+ employees
Real User
Top 20
Jun 27, 2025
Based on my experience with the TIBCO EBX solution, I advise users considering this solution to give it a try. They should explore it further and see if it fits into their requirement. If it does, then surely, it would be a great solution overall for them. I rate this solution 8 out of 10. The collaborative workflows where we have collaboration of different teams working at the same workflow helps to centralize our work within the organization. Our central team works on different workflows and with the business users. My application doesn't face the direct outside customer, but it deals with internal bank employees, where the four-eye principle needs to be implemented. All those validations and everything in the workflow from an end-to-end process can be configured in the EBX application itself. As an admin user, you can configure everything, including which step needs to come after which step and all configuration details from the development standpoint. Regarding the integration capabilities of TIBCO EBX, we normally transfer certain data. For instance, if you want to integrate, you can have data from the upstream because in a nutshell, EBX is the master data management tool. It could get data from some interface or deliver data to a certain interface; in the middle, it could enhance the data and implement various logic. You can schedule different kinds of jobs via EBX, and based on your scheduled jobs which you have triggered, it will run. If you schedule it for every day overnight or say a monthly batch job, then accordingly it gets triggered and delivers the data to the required interface. In terms of evaluating the performance of TIBCO EBX, particularly related to enhanced data quality or governance, when you trigger certain kinds of jobs, you can take a copy of the data and store it. However, it depends completely on the requirement. If the data size is too big and continues to store, it impacts the performance. After a certain time, it somehow impacts the performance due to the bulk of data in your table. But if you want to keep the basic details about when the job was triggered, it works efficiently. You can connect it with the database where you can store the basic details, replicate the tables and store them in the database as well, which you can use for any kind of SOX compliance or data governance matters.
System Engineer at a consultancy with 10,001+ employees
Real User
Top 20
Jun 26, 2025
We decided to switch to TIBCO EBX because we can organize the data, and it helps manage this data for an accurate and consistent view of the physical business data. When I compare it to MS Access, I'm not entirely sure, as I haven't used MS Access much. Every feature will have different requirements; during every sprint, we implement different features based on business requirements and then push from non-prod to production environment. I would advise other organizations considering TIBCO EBX that it is a new technology. This new tool can be used for data management perspective; unlike the old database, we are not heavily dependent on the SQL team for activities. Using TIBCO EBX, we maintain the application easily, ensuring high availability; if one goes down, we can activate the other one. I'm only working with this one tool. On a scale of 1-10, I rate TIBCO EBX a seven out of ten.
EBX DEVELOPER at a tech vendor with 201-500 employees
Real User
Top 10
Jun 25, 2025
TIBCO EBX is straightforward to use. Anybody with prior knowledge of using any web application can use it. It is essentially similar to filling out forms and submitting requests. On a scale of 1-10, I rate TIBCO EBX an 8.
I would rate EBX as a nine out of ten. Despite its resource allocation issues in Turkey, it is a great tool, being a new generation product with better capabilities than traditional tools.
I am the person who is responsible for caring for the deployment process for my company's clients, and I have noticed that most of my clients have been moving to TIBCO EBX from other solutions. I recommend the solution to those who plan to use it. I rate the overall solution a ten out of ten.
Senior Presales Consultant at a computer software company with 1,001-5,000 employees
Reseller
Oct 19, 2022
We would recommend this solution to enterprise sized companies, as well as midsized organizations that have sufficient available budget. There is also a cloud-based version of this solution, however, the on-premises version allows for greater control over the data environment, and so may be preferable for certain geographical locations. I would rate this solution an eight out of ten.
I would advise others that are wanting to implement TIBCO EBX they should try to build the data model from the beginning until the end. Take the time that they need, try to build as much as possible in the data model. It is best to build the workflow that they want at the beginning. They have to decide if they want history or data governance, or exactly which other part they want. It is important to build what they have and want on paper regarding the functionality of their core system before implementing it into TIBCO EBX. I rate TIBCO EBX a ten out of ten.
Sr Technical Architect at a computer software company with 10,001+ employees
Vendor
Oct 22, 2021
We're a customer and an end-user. Currently, we are one version behind. We're going to upgrade to the latest version maybe in two months, however, I'm not sure of the exact date. I'd advise new users to ensure they understand the scope of their implementation and applicability in their observation. I'd rate the solution at a seven out of ten.
Data Architect at a pharma/biotech company with 10,001+ employees
Real User
Jul 24, 2021
We're just customers and end-users. Whether I would advise another company to choose this solution or not depends a bit on the use case they are going to develop. I would say that, if a company has a basic use case, a basic means of getting data from a few sources like Oracle, SQL Server, Teradata etc., then maybe it is sufficient. However, if you are having an enterprise-level situation for SAP or Oracle Apps , it might scale up that well. Performance is also an issue as it does not optimize the underlying clusters to a great extent as compared of its competitors. One good thing is that, with the data model, you can just go and see the data model very well, to the most granular level and identify if there are any gaps. It also has a rich compare data model feature. However, again, for the workflow, you cannot edit it in the visual editor. You have to go back to that tree setup and there after complete editing during compile only one would be able to see if any errors has crept in or not. Having said that I would say the Workflows once created are very robust. There are some competing tools that allow the editing of workflows in the visual setup itself. That is very easy for users. If you can edit it in the visual setup, you can directly see the impacted upstream and downstream tasks or jobs in that workflow and conflicts if any. This speeds up the updating of the workflows by the data engineers or data stewards. I'd rate the solution at a six out of ten. The solution is average from an enterprise standpoint.
This is a rather technical solution and you must know that it takes some preparation before you can start working on it. In the future I would like to have a clean proof of the design of the data modem. It should be easy and visual. I will rate the solution an eight out of ten because I think there are some things to improve and that could be better.
TIBCO EBX is a versatile solution for businesses seeking efficient data management. It offers robust features like customizable workflows and dynamic data modeling, making it ideal for diverse industries managing complex data environments.TIBCO EBX caters to organizations looking to streamline data governance and management across departments. Its intuitive interface and seamless integration with external APIs make it easier for users to control data across domains. Efficient indexing...
I am not part of the PST team, so I have not been involved in that aspect. On a scale of 1-10, I rate TIBCO EBX an 8.
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.
Based on my experience with the TIBCO EBX solution, I advise users considering this solution to give it a try. They should explore it further and see if it fits into their requirement. If it does, then surely, it would be a great solution overall for them. I rate this solution 8 out of 10. The collaborative workflows where we have collaboration of different teams working at the same workflow helps to centralize our work within the organization. Our central team works on different workflows and with the business users. My application doesn't face the direct outside customer, but it deals with internal bank employees, where the four-eye principle needs to be implemented. All those validations and everything in the workflow from an end-to-end process can be configured in the EBX application itself. As an admin user, you can configure everything, including which step needs to come after which step and all configuration details from the development standpoint. Regarding the integration capabilities of TIBCO EBX, we normally transfer certain data. For instance, if you want to integrate, you can have data from the upstream because in a nutshell, EBX is the master data management tool. It could get data from some interface or deliver data to a certain interface; in the middle, it could enhance the data and implement various logic. You can schedule different kinds of jobs via EBX, and based on your scheduled jobs which you have triggered, it will run. If you schedule it for every day overnight or say a monthly batch job, then accordingly it gets triggered and delivers the data to the required interface. In terms of evaluating the performance of TIBCO EBX, particularly related to enhanced data quality or governance, when you trigger certain kinds of jobs, you can take a copy of the data and store it. However, it depends completely on the requirement. If the data size is too big and continues to store, it impacts the performance. After a certain time, it somehow impacts the performance due to the bulk of data in your table. But if you want to keep the basic details about when the job was triggered, it works efficiently. You can connect it with the database where you can store the basic details, replicate the tables and store them in the database as well, which you can use for any kind of SOX compliance or data governance matters.
We decided to switch to TIBCO EBX because we can organize the data, and it helps manage this data for an accurate and consistent view of the physical business data. When I compare it to MS Access, I'm not entirely sure, as I haven't used MS Access much. Every feature will have different requirements; during every sprint, we implement different features based on business requirements and then push from non-prod to production environment. I would advise other organizations considering TIBCO EBX that it is a new technology. This new tool can be used for data management perspective; unlike the old database, we are not heavily dependent on the SQL team for activities. Using TIBCO EBX, we maintain the application easily, ensuring high availability; if one goes down, we can activate the other one. I'm only working with this one tool. On a scale of 1-10, I rate TIBCO EBX a seven out of ten.
TIBCO EBX is straightforward to use. Anybody with prior knowledge of using any web application can use it. It is essentially similar to filling out forms and submitting requests. On a scale of 1-10, I rate TIBCO EBX an 8.
I would rate EBX as a nine out of ten. Despite its resource allocation issues in Turkey, it is a great tool, being a new generation product with better capabilities than traditional tools.
I am the person who is responsible for caring for the deployment process for my company's clients, and I have noticed that most of my clients have been moving to TIBCO EBX from other solutions. I recommend the solution to those who plan to use it. I rate the overall solution a ten out of ten.
I rate the product a six out of ten.
I rate TIBCO EBX an eight out of ten. We have four administrators that maintain the solution.
We would recommend this solution to enterprise sized companies, as well as midsized organizations that have sufficient available budget. There is also a cloud-based version of this solution, however, the on-premises version allows for greater control over the data environment, and so may be preferable for certain geographical locations. I would rate this solution an eight out of ten.
I would advise others that are wanting to implement TIBCO EBX they should try to build the data model from the beginning until the end. Take the time that they need, try to build as much as possible in the data model. It is best to build the workflow that they want at the beginning. They have to decide if they want history or data governance, or exactly which other part they want. It is important to build what they have and want on paper regarding the functionality of their core system before implementing it into TIBCO EBX. I rate TIBCO EBX a ten out of ten.
We're a customer and an end-user. Currently, we are one version behind. We're going to upgrade to the latest version maybe in two months, however, I'm not sure of the exact date. I'd advise new users to ensure they understand the scope of their implementation and applicability in their observation. I'd rate the solution at a seven out of ten.
We're just customers and end-users. Whether I would advise another company to choose this solution or not depends a bit on the use case they are going to develop. I would say that, if a company has a basic use case, a basic means of getting data from a few sources like Oracle, SQL Server, Teradata etc., then maybe it is sufficient. However, if you are having an enterprise-level situation for SAP or Oracle Apps , it might scale up that well. Performance is also an issue as it does not optimize the underlying clusters to a great extent as compared of its competitors. One good thing is that, with the data model, you can just go and see the data model very well, to the most granular level and identify if there are any gaps. It also has a rich compare data model feature. However, again, for the workflow, you cannot edit it in the visual editor. You have to go back to that tree setup and there after complete editing during compile only one would be able to see if any errors has crept in or not. Having said that I would say the Workflows once created are very robust. There are some competing tools that allow the editing of workflows in the visual setup itself. That is very easy for users. If you can edit it in the visual setup, you can directly see the impacted upstream and downstream tasks or jobs in that workflow and conflicts if any. This speeds up the updating of the workflows by the data engineers or data stewards. I'd rate the solution at a six out of ten. The solution is average from an enterprise standpoint.
This is a rather technical solution and you must know that it takes some preparation before you can start working on it. In the future I would like to have a clean proof of the design of the data modem. It should be easy and visual. I will rate the solution an eight out of ten because I think there are some things to improve and that could be better.
I would recommend this solution to others who are considering it. I would rate it a ten out of ten because it's the best.