Collibra Governance Reviews

Collibra Governance reduces the time-consuming aspects of the process. You'll need only one-fifth of the team as it'll depend on two to three people, and that's really important to businesses.

I find the metadata feature valuable because it replaces the coding. The metadata creation happens via Collibra, and it reduces the code. 

We have an issue with metadata history. If someone changes the metadata, we can't see who changed it. But they are trying to upgrade the system with this feedback and are still working on it. We are still waiting for a proper log to maintain the solution.

I have been using Collibra Governance for the last four years.

I haven't found any limitations or obstacles with scalability. It completely depends on who is managing the solution. We have placed Java resources, and we didn't face any limitations with that. 

On a scale from one to ten, I would give their technical support a seven. 

This is because they still haven't completely provided the solutions we asked for. They're a new product and are lacking in some areas. They can provide 80 to 90%, they have fixed some things in the public sector, but there are some gaps. 

If you're going to start a completely new project, the deployment takes at least six months. But if you're looking to establish particular effective information governance or something like that, it could take maybe 10 to 20 days.

We have had a return on our investment because we don't use the same manpower that we used to for the code.

Before using Collibra Governance for metadata development, you need a business analyst with extensive domain expertise. Collibra Governance is just a metadata creator. You need business knowledge to understand how you're going to create the metadata and how it will link with your business applications.

Collibra Governance isn't the only part where you're going to develop everything. Collibra plays a major role, but you still have to add other components. For example, you need Java resources, Oracle and you need to integrate all this stuff into the Collibra before making the project list.

It demands a high level of visibility. The technology component idea, database knowledge, and more should be made available to a select group of people. If that's not there and everyone is new, and you're using Collibra Governance for the first time, you're going to have many problems.

The teams should have proper knowledge of background modeling, and they should have proper knowledge of the existing business. If they're creating a completely new team and the new team doesn't have any business knowledge, expect project failure.

On a scale from one to ten, I would give Collibra Governance an eight.