Denodo Reviews

My primary use case is for data virtualization. I'm working in the pharma domain, so there are large amounts of data coming in from different sources, which I aggregate into Azure SQL, some other web services, and SAP applications like CRM, POS, and others. Denodo acts as a virtualization layer, where we are collecting and creating views for analytical purposes. So we use Denodo to integrate and transform. It is deployed on-premises. 

The most valuable feature is the performance. Denodo is very useful, especially in this huge pharma environment. I've found that older SAP solutions were very tightly coupled to each other, which resulted in data restrictions. Getting data from different sources was tough and tedious. Compared to these old solutions, Denodo is very easy to work with for the analytical team. Now that we've implemented this virtualization layer, we are capable of getting the data very smoothly. We implemented a very small unit, but the performance and integration have been very good. 

Denodo's training documentation could be improved by providing more material. From an administrative standpoint, I've found that only Denodo websites provide the usual tutorials. It may be because it's a bit of a restricted tool, but it results in trouble with learning. Normally, I can find help and solutions from other sources, but I haven't been able to find any for Denodo. Other that, it's fine and it performs well. I only have six months of experience, so I can't accurately suggest improvements. 

I have been using Denodo for almost six months. 

Currently, we haven't found any discrepancies or problems with stability. We are a team of 25 using Denodo simultaneously, but we're still in a development and testing environment. Once it's in production, we'll be able to tell if there's any kind of a bottleneck. 

Our Denodo administrative team created a pipeline from one environment to another environment and we haven't had any trouble yet. The production deployment is going to happen soon, so within a month or so we'll have a better understanding of the production data, streaming data, and all that. 

Technical support is fine. I will say that my team and I are interested in pursuing a Denodo certification. I was looking for a way to take the Denodo Administrative Certification 8.0, but I'm still waiting on that. Developers are restricted right now because we need to pay for each and every topic in Denodo. 

I have worked with Azure Data Factory. With Data Factory, you need a staging solution, a physical data platform for storage. Denodo doesn't need this, since it has a cache mechanism. 

I have also previously worked with TIBCO, but that was more service integration than data integration. 

The initial setup was easy. Also, connecting Denodo to Power BI was a smooth process. It was simple to connect it with a Denodo ODBC connector. So installation and connecting with other tools were both very easy. 

For deployment and maintenance, we are a team of two developers. It took around eight months to develop the unified views. 

I implemented through an in-house team. 

I rate this solution a seven out of ten. I work in an advanced analytical area where it helps to reduce bottlenecks, extract from different application sources, improves performance, and gets the desired data, which is what those endpoint people need. 

If you have a vast data fabric or data mesh architectural framework, I definitely suggest implementing this kind of a virtualization layer. I recommend Denodo because it has been very easy, compared to other integration platforms. 

Currently, we're working for one of our industrial resource clients. It is a hospital-based company that does resources and mining worldwide. So we use Denodo to create views for multiple courses so that clients can review them within two seconds.

We use Denodo to build our views. Before our views relating to GBT ODBC, we sometimes used mosquito bites and XML or flat files.

The ability to transfer data is very valuable. It is one of the best when considering other ETL tools and is easy to maintain. Compared to Informatica and Oracle Data Integrator, Denovo is the most convenient.

We can't scale it to meet digital requirements.

We have been using this solution for one year.

It is a stable solution.

It is a scalable solution.

It has a very straightforward setup. However, in some cases, it may take some time, depending on the database and variety of data.

I rate this solution an eight out of ten.

We use Denodo in our organization whenever a web service is needed quickly, or where using another technology (such as Java) would take too much time. From our standpoint, Denodo is used in such a way that any consumer can build their own web service based on their data points. There's no need to ask the provider, "I need a web service for X, Y, or Z". Instead, you simply ask, "Hey, I just need the data points". For example, for a table, all you need is to ask the consumer to provide the table name and for whatever service you need, you can build your own web service on top of it.

It takes minimal effort to accomplish this with Denodo and it's an extremely quick process, especially when compared to doing the same thing with Java or any of the other technologies we are using. In fact, you can build a web service with Denodo within 10 minutes. Our web services can also be consumed via different methods where there are multiple possible levels of responses, and each web service can be duplicated to provide for each different level of response. So within 10 minutes, you can build a web service with different variations out-of-the-box. 

If you wanted to incorporate just one method in Java or AWS, it would take at least a day to deploy and have it set up to provide responses. But our experience with Denodo is that it only takes a few clicks and it will instantly deploy the web service, and then you are free to use that resource. 

As for our environment, there are two editions that we have the option of using. One being the cloud-based version, and the other is a client version which we can download onto our system. Most of our organization is using the cloud-based version, as all the patches are pushed directly to the cloud. Overall, we have about 100+ company members using Denodo, most of whom are product developers.

We have web services created for each of our applications, and ordinarily the creation of these web services would be dependent on the provider. We would previously ask our providers, "We need web service X, Y, or Z, and we need it by this deadline. Can you produce it by that deadline?" But now, the person who needs the web service can simply build their own based on the data points they are looking for. This kind of mindset is the main reason why we chose Denodo.

The best thing about Denodo is that creating and deploying a web service can be done in about 10 minutes, compared to a whole day when it comes to other solutions (such as when deploying with Java and AWS).

It's also really easy to do so in general, because no longer do you need to request the specifics of how the web service is to be created, but instead all you need to do is provide the data points needed and you will have access to a web service that is ready to serve you responses.

Not only that, but you will also be able to duplicate the newly-created web service to be used in different ways with various methods. And all this takes only a few clicks on a single platform, as long you know the data points that you need.

There are a couple of areas that can be improved in Denodo. From a stability point of view, sometimes we see issues in the data management functionality. This only happens now and then, however, and usually takes place when we add in our own customization.

There are also certain limitations on customizing Denodo, in general. It would be better if Denodo provided more mechanisms for users to develop custom products where they could easily build in their own logic with automated means. In the case of complex customization, we will usually use Spring Boot instead of Denodo, especially when we have tons of data in production and we need to segregate it based on certain logic. Otherwise, when it's a matter of minimal data points that are required, we will simply build it as a web service instead of writing the same logic in Spring Boot.

A feature that we have wanted since we started with Denodo is to have a fallback option. After we migrated all our web services to Denodo, it would have been nice to have a ad-hoc fallback option where if we ever do want to use something else, that option is available. For example, something where we have those built-in read-only views which we can reuse and, without too much time or fuss, build a web service on top of that by simply plugging in views, details, or any other part of the Denodo platform architecture.

I have been using Denodo for one year now.

At certain times we have seen some stability issues with the data management within Denodo. It's not all the time, of course, but only sometimes.

When it comes to more complex scenarios, we will typically use Spring Boot instead of Denodo to accomplish our needs. Usually, this happens when we have tons of data in production and we need to segregate it based on some logic.

With regard to scalability, we have different scaling strategies for two of our main products that we're working on. There isn't much difference in data points between these two products, but when it comes to the refreshing of the data, one of the products is refreshed on a minute-to-minute (or second-to-second) basis. With this product, the scalability of Denodo isn't fully up to the mark.

However, on the other product, we have no challenges whatsoever in terms of scalability, especially in terms of response times and accuracy. We have built a lot of web services on top of it with Denodo. 

When we purchased Denodo, our architects had a discussion with their support team based around what would be needed to improve things, such as scaling up at a later stage, and they were happy to help us out. We also occasionally write them emails whenever we encounter a challenge such as a code glitch, but otherwise there is no further direct interaction with them for the most part.

Denodo is one of the only products we have come across where the consumer can build in a web service without being dependent on the product team or anyone else. If you know the table name, or the data points needed, you can directly go ahead and import the schema and build your web service. Crucially, you don't have to wait for someone else to come and help you build the web service, which ultimately reduces the dependencies between our different teams.

This is, in fact, a main focus point we have come across in our work. In terms of data points, we will typically see 100+ data teams working with independent databases with no platform to connect them all. With Denodo, we can connect hundreds of databases with the data point connection, and it's all drag-and-drop to connect tables from whatever database we need. Then we just export the web service on top of it.

You can contrast this process with Spring Boot where you would instead need to go to a specific team and get access from them first. They would then have to take the name of the table and report it elsewhere in another format.

Of course, we also prefer Denodo for the simple reason that it is cross-platform across the different platforms we typically work with, which have extremely specific conditions when it comes to handling data.

The setup includes what is essentially a kind of software installation. If you go for the cloud-based tool, it's not much of an installation at that, because you just plug in your databases and you're ready to start working with it.

It's very easy and very fast. Basically, you are just plugging in the databases and setting the location of the cloud-based URL which will be shared by your team.

Denodo provides a lightweight 30-day free trial, but when we do courses on top of it, it costs $150 for each person. Even if you're not purchasing the product, I believe there is some kind of reward they will give you in the initial stage.

I, personally, am doing a couple of courses with them and each course costs a different amount depending on the level of the course, such as beginner, medium, or senior. The initial course level costs $150 and the mid-level course goes to $200, and I have seen a couple of courses at $350 as well. These costs are incurred as you enroll in a single course, which lapses after six months.

To people thinking about using Denodo, I would say that you should be clear about whether it fits the level of your architecture in terms of scalability. In cases where you have a low-level architecture, you shouldn't expect to get more results out of it simply by using Denodo.

Essentially, when you're building a product, your environment should be appropriately scaled to fit that product, and Denodo is built for the enterprise level, not for small-scale inter-system users. For example, in our organization, we use Denodo for its web services functionality, but when it comes to similar products in the realm of event streaming, for example, we will instead use other tools such as Apache Kafka, as appropriate.

I would rate Denodo a six out of ten.

We use the solution for data virtualization to publish the data as a product. We have different teams who have their own database. If a team needs any data, they get it from Denodo.

It is easy to virtualize data using the solution. If required, we can also use the solution for caching.

The solution is slow when there are many virtualization layers. The solution is also slow when we connect the on-premise solution with the one on the cloud through a network gateway.

I have been using the solution for two and a half years.

The product is stable.

More than 100 people in the organization are using the solution.

As a developer, I can easily set up the solution on my local Kubernetes. Local configuration is pretty easy.

A lot of virtualization leads to data latency. We can do caching on the intermediate layer. We can also leverage Databricks if we have any complex transformation.

I have a local Docker container. I can easily integrate my local container through Git repo and clone it in our depth server. Denodo is the only tool I know for data virtualization. I will recommend the solution to others. Overall, I rate the product a ten out of ten.

Denodo is a tool used for data virtualization. Our company provides services to our customers. One of our customers is on the Denodo platform.

Denodo is lightweight in terms of how it leads you to combine your discrete data systems in one spot. You are able to logically define and create your desired data set without actually getting your data shifted from the data system like any trivial ETL system does. It will not perform any data movement.

The solution provides ease for accessing data in various ways, including on-demand APIs. Uploading your data on an API will take less than an hour.

Denodo provides a good experience in terms of data visualization. The data on demand is the best feature. I also enjoy the go-to feature for data fabrication, or data mass structure, where data democratization is being sent data for all people at that time.

There are a few cosmetic changes that would make Denodo better, including offering holistic governance. It would be beneficial if you could see what inquiries are going around Denodo on the remote system, including who has logged in and which one is using which part of the deviant spaces. 

Denodo has provided several modules with their scheduler that also have room for improvement. 

When thinking about future releases, Denodo should consider their platform availability because our administrator has seen some challenges in this regard. It requires some optimization on the developer side as well. 

Denodo would benefit from having a more user-friendly view. It would be good if the solution provided a much-needed cellular platform.

I have been using Denodo for five years.

The stability of Denodo is okay. You will encounter some load optimization and performance tuning, so you do need some technicality around your data pack. 

The scalability is there. With AWS, there is elastic computing that manages scalability.

We currently have over 200 people working on Denodo. This includes our customer's manufacturing organization as well as people from business intelligence and analytics. They consume data directly from Denodo.

Customer service and support with Denodo is quite good. Our concerns are resolved and addressed on time. Overall, I would rate Denodo's technical support a four out of five.

Positive

The initial setup of Denodo is straightforward. The time it takes to deploy depends on each scenario. If you are looking for an inspired level of adoption, that will require time to model the data. However, if you are looking to use Denodo on a more simplified basis, deployment will not take longer than a couple of weeks.

Being an architect, I would rate the ease of setup a four and a half out of five.

Denodo typically provides a positive ROI within six months.

Licenses are available for the solution manager or for one of the components. It is a fixed price license for those that connect. The cost for Denodo is in line with other similar products.

The first comment I have for anyone considering implementing Denodo into their organization would be to ensure they understand that they should not expect ETL from Denodo. ETL is an old concept of data integration, while Denodo is the latest version. 

With Denodo, there is no need to further your ETL workflows. The workflows will be created in parallel, and you will realize how the Denodo implementation is setting it up to replace your ETL flow. You do not need to smooth or attach anything to what is currently running. By working in parallel with what the Denodo system is using, you will be able to copy across your users on Denodo and realize virtualization over your ETL. 

Overall, I would rate Denodo an eight out of ten.

We have around 100 people using this solution in my company. The solution is deployed on cloud and on-premises.

The most valuable features are query optimization and the single language independence from the sources we're using to catch data.

I would like to see a proper way to avoid killing the sourcing systems. There is some parameterization in this case if you push down the query to some systems, but I think there are still issues with giving this tool to end users because they could write queries that could cause a lot of issues in the operation systems.

I have worked with this solution for more than two years.

It's quite stable.

It's scalable.

I would rate technical support as four out of five.

We compared this solution with TIBCO. We chose to go with Denodo because we had some daughter companies that previously used TIBCO and gave us some feedback about it.

Setup is simple on the cloud. The on-premises setup could be more complex depending on the security firewalls.

I would rate this solution as nine out of ten.

I think the business metadata should be available to help people understand what kind of data is being connected. This makes it difficult for end users to use Denodo.

I would recommend this solution to those who are interested in it.

I mainly use Denodo for data modification.

Denodo's best features are its performance, easy data transformation, and the job scheduler. 

Denodo has some difficulty supporting large numbers of records. Its error reporting is also unreliable and doesn't give clear information on the problem. We've also recently had an issue with roles getting deleted.

I've been using Denodo for almost fifteen months.

We've recently had some problems with slowness and instability. 

Denodo is scalable.

The initial setup was easy and took about an hour.

I would rate Denodo seven out of ten.

I am using Denodo as a data integration and management tool. The concept behind Denodo is data virtualization, which makes the retrieval of data available faster. The availability of data in real-time is much faster as compared to directly accessing the data from the web.

The virtual layer or Symantec part of it are most valuable. Where all the data sources, which we integrate together, are available on a virtual layer and that makes it faster.

I would like to see a connectivity option with third-party apps, for example, JDBC, and ODBC drivers. Currently, we need to install it separately from the Denodo side and then connect it. If they provided an option directly in Denodo to connect to these Power BI, and Tableau, Denodo would be even stronger. Microsoft provides SharePoint, and they have this option where you can directly connect to Power BI, and you can directly connect to the visualization tools. If Denodo can do this, then it would be great.

I have been working with Denodo for over one year.

Denodo is very stable. I started working with Denodo a year ago, and I have not come across any issues.

The technical team of Denodo is really good. They are very helpful. I had some issues because I was doing my first project, but the Denodo team is cooperative and supportive. They immediately helped me with whatever issue I was facing. I just had to email them, and they responded immediately.

Positive

It is very straightforward and easy. They provide hands-on training and proper documentation. Their knowledge base is detailed and easy to understand and learn.

Both options are available. The Denodo team can directly do it for you, or you can do it from a third party who is experienced in it. It takes one day, less than one day. You just need to know the right requirements from the customer for whom you want to deploy the Denodo platform, how many servers they want, and what type of installation they want. It depends on the customer, but the deployment is easy.

There is an express edition and an enterprise edition. For customers, obviously, we provide them with the enterprise edition. Students can use the express edition and it is free to download.

I would suggest having basic knowledge about data. For example, what are the different types of data sources? And what is a data warehouse? The fundamentals of data science. The basic knowledge as well as having an understanding of Structured Query Language, because Denodo uses a query language that is called Virtual Query Language, and it is similar to that SQL. I would rate Denodo a nine out of ten.