Denodo allows us to create and combine new views to create a virtual repository and APIs without a single line of code. It is excellent because it can present connectors with a view format for downstream consumers by flattening a JSON file. Reading or connecting to various sources and displaying a tabular view is an excellent feature. The product's technical data catalog is well-organized.
I strongly recommend it for general management of personal data privacy programs and risk and contract management, it complies with all major world legislation in addition to being easy and fast. Not recommended for data discovery still requires refinement.
Caching - but I am sure it will be improved by now. There were times when we expected the cache to be refreshed but it was stale.
Schema generation of endpoints from API response was sometimes incomplete as not all API calls returned all the fields. Will be good to have an ability to load the schema itself (XSD/JSON/Soap XML etc).
Denodo exposed web services were in preliminary stage when we used; I'm sure it will be improved by now.
Export/Import deployment, while it was helpful, there were unexpected issues without any errors during deployment. Issues were only identified during testing. Some views were not created properly and did not work. If it was working in the environment from where it was exported from, it should work in the environment where it is imported.
We have used a shared hosted tenant managed by OneTrust for over three years with only one instance of a lengthy (4+ hours) unexpected outage which happened years ago.
Denodo is a tool to rapidly mash data sources together and create meaningful datasets. It does have its downfalls though. When you create larger, more complex datasets, you will most likely need to cache your datasets, regardless of how proper your joins are set up. Since DV takes data from multiple environments, you are taxing the corporate network, so you need to be conscious of how much data you are sending through the network and truly understand how and when to join datasets due to this.
We selected a European hosting location based on our initial use case, however, our usage of the OneTrust platform has expanded globally to where the majority of users sit in the Americas or Asia-Pacific regions. There is a noticeable lag when navigating the platform for users located far away from the hosting location.
As a user, you can mitigate any sluggish response time by the aggressive use of multiple browser tabs. I commonly have one tab open on an Inventory detail screen, another tab on an Assessment window, and maybe another tab on a customized inventory list screen. If one tab is slow I hop to another tab and work on that tab while the first tab responds.
Both our customer rights access and cookie consent advisors were responsive and helpful in getting us trained on using the platform and the various assets implemented on our website. We had multiple training sessions that were more than enough in getting all of the users on our team familiar with what we needed to do.
An implementation specialist worked with us remotely during our initial deployment. Due to the diverse geographic locations of my organization's participants, the implementation and training had to be done remotely (this was before COVID-driven remote work).
The implementation specialist was knowledgeable and helpful but to really get full benefit from the platform I encourage organizations to dedicate a specialist within your company to really study and learn the platform.
First, when we compare OneTrust Privacy and Data Governance Cloud to the software I mentioned above, OneTrust Privacy and Data Governance Cloud software was way more affordable than the other 2. Also, along with the other 2 software, OnTrust was one of the most user friendly tool/software we've ever used.
The platform has exceptional capabilities to customize the user interface, reports, and recorded information. In most cases, the customization can be compartmentalized so that if the customization performed for Department A is determined to not impact Department B, the customization can be hidden from Department B.
We have four different departments using the IT Risk Management module. Three departments share their work in what we call the 'shared data risk management zone'. Another department is using IT Risk Management for a bespoke portfolio risk management task, and the customization for this department is largely hidden from the other departments.
