I don't use Denodo, but we are in contact with this product. I am involved in decision-making around Denodo and I am considering this solution.
Denodo 9 Enterprise
Denodo Technologies Inc.External reviews
External reviews are not included in the AWS star rating for the product.
Virtualization has improved query speed and cost savings but proof of concept remains unclear
What is our primary use case?
What is most valuable?
I saw a demo showing that Denodo doesn't require any storage and the query performance is very fast. Denodo has a virtualizing feature that eliminates the need for storage and allows for better query planning, resulting in faster performance than ever before.
Denodo's virtualization feature is beneficial for many siloed databases as it links them well, making it useful.
Denodo has positively impacted my organization through cost savings. Saving time and resources is important to me when discussing Denodo. The fast query performance of Denodo means saving time.
What needs improvement?
If Denodo could make the POC period more solid and clear so that more people can try using it, I think that would help significantly.
It would be better if Denodo could clearly explain to customers what advantages virtualization technology has over general other data warehouse technologies.
I don't have anything more I want for Denodo beyond what I've already mentioned.
For how long have I used the solution?
I've worked in this field for five years.
What was our ROI?
I want to exit this investment in Denodo as I haven't seen a return on investment.
What's my experience with pricing, setup cost, and licensing?
I'm not sure about Denodo's pricing or any setup costs and licensing. I don't know about the pricing of Denodo yet.
Which other solutions did I evaluate?
I compare Denodo with other solutions and I don't know which is the best.
I would advise others looking into using Denodo to compare it with other solutions and ask more questions about the virtualization feature.
What other advice do I have?
We only have a business relationship with Denodo as a customer.
I am interested in being a reference for Denodo. Denodo should not contact me if they have any questions or comments about my review.
Please use an anonymous name when publishing my review. I don't want to use my real company name in the review as we are just comparing this solution.
My review rating for Denodo is 7.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Outstanding Virtualization and Query Optimization Features
Has simplified multi-database querying and accelerated solution delivery with minimal setup
What is our primary use case?
I used Denodo for a few months early this year, from January to March. My main use case for Denodo during that period was visualizing data from Snowflake and other databases across multiple databases and doing various types of analytics on the data inserted in those databases. We used Denodo for getting the data across multiple databases and matching the data in between these databases to have a single entry point for our queries.
For example, we had a bunch of files arriving on Azure Data Lake Storage, and we needed to match when these files arrived to what we needed to do with those files that were stored in a Snowflake instance. So, we used Denodo to cross this data and select queries, and then apply the Azure function that we needed to do to these files that were arriving on our Azure storage.
What is most valuable?
Denodo offers a great query language, the VQL, which was very easy to understand for someone that only knows SQL. It was easy to work with, and it was easy to integrate various types of databases in general. The usability of the platform is very great. The federated queries were also a feature that I used a lot. The easy usability of Denodo helped my work and made things easier for productivity. We were able to ship code faster than if we needed to use another type of data visualization tool or even an ETL.
When we have multiple databases, the standard or common approach is just to have an ETL that matches the data, and we need to write this whole ETL. With Denodo, we can simplify this whole work to a few queries or setups in the databases and just make a few queries. This was actually easier, and it was faster to deliver a solution for a client instead of building a whole ETL pipeline or simply backfilling one database in another. Denodo simplifies your work and helps you ship code or ship solutions in a faster way. I really like the UI that Denodo has on the web app version. It was very simple and actually very beautiful to see. For a complicated program, it was very easy to understand how it works, even for someone who is just approaching the data engineering career or side of the programming language.
What needs improvement?
The desktop version of the Denodo app has a difficult UX to understand, touch, and set up. But they have fixed that on the web app version, which is nice. Overall, the platform works great with the current setup that they have. I didn't really get to know the quirks and the bad side of the platform, as I've only used it for three months. In my opinion, it's a great software, and it's not buggy at all. The interface is simple and easy to understand.
For how long have I used the solution?
I've been working in my current field for eight years right now.
What do I think about the stability of the solution?
Denodo is stable.
How are customer service and support?
The customer support for Denodo is great. They are very easy to work with, and all my questions and concerns were answered in a very short amount of time.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I didn't previously use a different solution before Denodo. When I saw Denodo for the first time, I thought it was great, but it was not my choosing to use Denodo; it was the standard platform for the company I was working at.
How was the initial setup?
We use Microsoft Azure as the cloud provider for Denodo's private cloud deployment.
What was our ROI?
I can't share any metrics with you because I was just a developer. But my general impression is that yes, Denodo saves a lot of employees and development time. Because if you don't need to write a whole ETL to make the data virtualization, you need way fewer people to write a query instead of writing an ETL pipeline.
What's my experience with pricing, setup cost, and licensing?
I didn't really manage the setup cost, licensing, and pricing for Denodo. But in my opinion, it's very expensive. For small companies, it's not a solution that most small companies can afford. But for big companies, the pricing seems fair. It would be nice to have a cheaper version of Denodo for small businesses.
What other advice do I have?
My main advice is to read the documentation for Denodo. It's a very powerful solution, but it has a lot of quirks and a lot of things that can be done and should be done the right way to have better performance when using Denodo. The documentation is very clear and will help you 99% of the times. The review rating is 9.
Instant Unified Data Access, No ETL Required
Denodo is great
Denodo is a great platform for me, it offers the best in class data management solution
Denodo is an excellent solution for big data challenges, through its data virtualization platform.
Data virtualization and integration enabled while caching and scalability room for improvement
What is our primary use case?
Denodo is designed for a distributed data fabric. Instead of a centralized data lake, we are in a distributed data mesh. Whenever a team wants to publish some data product, they are publishing data through Denodo, and their data store might be different; it might be in Azure SQL, in an Azure Databricks data table, or in ADLS.
Whenever a user is looking for data, instead of connecting to each individual data source, they can only pull data through Denodo views, which is a virtualization layer. Role-based access control can be implemented. Not everybody can pull data; whoever is looking for data and whatever data they are looking for, that approval we can give, and based on that, they can pull.
For real-time analytics, we have an Azure Kafka endpoint. There are some use cases with the Azure Kafka endpoint; we have transferred data through that, and through Databricks, we have transformed the data and stored it in some persistent layer such as a Databricks data table or any other data store.
What is most valuable?
One of the best features of Denodo is that it's one unified layer. All programmers or software need to manage different endpoints through one Denodo endpoint. We have custom-developed a tool called Marketplace where we can see whatever data products are available. It is centralized through one portal, a one-stop shop.
Denodo supports SQL base, so if you want to join two tables or two views, you can use SQL, which is an advantage as most developers or business people know SQL. The distributed data mesh functionality allows teams to publish data products through Denodo, regardless of their data store type.
Role-based access control is another valuable feature, allowing selective data access based on approval. The Azure Kafka endpoint enables real-time analytics capabilities.
What needs improvement?
In terms of improvements for Denodo, regarding performance, in cases where there are multiple virtualizations—such as reading from one Denodo view that is virtualized, and from that view there's also virtualization, and another team is reading from that view—if multiple virtualizations happen with no caching in between, it becomes slow.
This occurs because it is cascading; whenever at the top level someone is reading data, that request is getting cascaded to the nth level, causing issues, especially in cases such as Power BI reports. We need to consider implementing some persistent layer in between.
The scaling process should improve because many things are getting automated. The scale-out part needs to be automated, though I am uncertain whether Denodo has already implemented that feature.
For how long have I used the solution?
I have been working with Denodo since joining this organization, which is two and a half years. I believe the organization has been using Denodo for five years.
What do I think about the scalability of the solution?
Denodo is scalable and is installed on a cluster, enabling scale-out capabilities. However, it cannot be scaled on the go. For huge data requests, it cannot scale automatically; admin action is required. The scaling process should improve as many things are becoming automated. The scale-out part needs to be automated, though I am uncertain whether Denodo has already implemented that feature.
How are customer service and support?
I would rate Denodo's technical support an eight out of ten because whenever there is planned maintenance or if the Denodo server is down, we receive emails from the support team. If we raise a ticket, it can be resolved or addressed within a reasonable time frame, so support is good.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I am not certain what was used before Denodo as they had started using it before I joined. At that time, they might have had some legacy systems, and each team had their own ETL pipeline.
What other advice do I have?
We are not using AWS, and a different team is responsible for onboarding or approving new software or licenses. Regarding advanced metadata management features, someone from the Denodo SME or Denodo admin team would be better positioned to comment.
We have used the caching mechanism. For huge data sizes, we are using Snowflake. Denodo has the feature to persist data in any data store. While Denodo doesn't typically persist data as it's a virtualization layer, we can persist data in Snowflake for large datasets.
Denodo can be deployed both on-premises and in the cloud. Initially, they started on-premises with the Denodo server, but have now migrated to the cloud. Denodo is the backbone for the BU I'm working for. If someone wants to share data or bring data, they need to go through Denodo, making it the backbone of this data mesh architecture.
I am not familiar with Denodo's pricing as that is handled by the budget or senior management team. We might be a partner of Denodo, but I'm not certain about this relationship. We are using Databricks Spark, not core Apache Spark.
I would rate the product overall an eight out of ten. I am satisfied, but there is always scope for improvement. If they fix scalability automation and virtualization problems, I would give them a higher rating.
Data Virtualization Expert
Fantastic Virtualization Tool to enable Operational & Analytics Reports for those have More sources
Tool is very much useful for self service development and deployment for citizen developers.
Denodo is Great not only for virtualization but Enabling API, Data Extracts, Catalog etc.
By using Denodo we solved this problem and provided real time data to users even we have so many source system combined together to produce the reports.