Decube is being used to build a data glossary, data catalog, lineage, data monitoring, and observability. After using Decube for three to four months, I believe it looks good now. It operates at the SaaS level, so you simply connect the data sources and it builds a catalog with observability and schema drift detection. The tool provides all of that functionality in a seamless manner.
Data lineage has improved visibility and monitoring now detects issues and alerts teams quickly
What is our primary use case?
What is most valuable?
The data lineage chart is definitely helpful because it allows us to traverse how data flows from the source to the report layer, providing full visibility of how the system works.
Regarding automation, automated data health checks are valuable. If there is any drift, data quality issue, data over-range issue, or missing data, the tool detects it and sends notifications to the concerned team. Alerting mechanisms are available through multiple channels including email.
Decube generates reports regarding what has happened. Through the API capabilities, I can build monitors, glossaries, and linked assets, which has been very helpful. The API capability is supporting a lot of functionality.
Regarding data governance, Decube does help improve it in the company. Once it is fully available, it will definitely help the whole team by providing visibility into which data is coming from where and by addressing any reporting or data quality issues.
What needs improvement?
There are a few drawbacks to the product. If I delete any record, it is not immediate and does not allow me to create the assets again. The system indicates that the asset is already available. We are checking with the team to understand what the problem is.
Another issue is that if there are system-level monitors, there is no way to update them through the API, so API support is needed for them.
For how long have I used the solution?
I have been working on Decube for the last three to four months.
What do I think about the stability of the solution?
I did not see any stability problems as of now because we are not yet in production. In the development environment, everything looks good.
What do I think about the scalability of the solution?
How are customer service and support?
I have dealt with technical support from Decube. Regarding the effectiveness of technical support, they are helpful and doing a good job. If I would rate support from zero to ten points, I would give them seven. They connect us through email and Teams chat. We get responses, though there is some delay, but at least we receive responses, so I would rate them at six or seven.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I have worked with Collibra previously, but I am currently working on Decube. I have been in the data governance and IT products sphere for three to four years and have worked with Ranger and other tools.
How was the initial setup?
Regarding the installation of the product, I do not have experience with it as it is a DevOps activity. Decube is Kubernetes-based, and both Decube and our DevOps team support it.
What about the implementation team?
I work as an integrator.
What was our ROI?
Regarding ROI, it is yet to be proven. We are exploring the tool for the last three months and are yet to be in production, so only then will we know what benefit we are providing to the client.
Which other solutions did I evaluate?
I am currently using Decube for data governance. I have worked with Collibra previously, but I am now working on Decube.
What other advice do I have?
Currently, I work with other tools on various data governance activities. For data governance specifically, Decube is the only tool I am dealing with.
Which deployment model are you using for this solution?
Hybrid Cloud
