Denodo OverviewUNIXBusinessApplication

Denodo is the #2 ranked solution in top Data Virtualization tools, #3 ranked solution in top Cloud Data Integration tools, and #8 ranked solution in top Data Integration Tools. PeerSpot users give Denodo an average rating of 7.4 out of 10. Denodo is most commonly compared to Azure Data Factory: Denodo vs Azure Data Factory. Denodo is popular among the large enterprise segment, accounting for 74% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a financial services firm, accounting for 16% of all views.
Denodo Buyer's Guide

Download the Denodo Buyer's Guide including reviews and more. Updated: November 2022

What is Denodo?

Denodo operates in the data virtualization field– providing high performance, unified access to the broadest range of enterprise, big data, cloud and unstructured sources, and the most agile data services provisioning and governance – at less than half the cost of traditional data integration. Denodo’s customers have gained significant business agility and ROI by creating a unified virtual data layer that serves strategic enterprise-wide information needs for agile BI, big data analytics, web and cloud integration, single-view applications, and SOA data services across every major industry

Denodo Platform offers the broadest access to structured and unstructured data residing in enterprise, big data, and cloud sources, in both batch and real-time, exceeding the performance needs of data-intensive organizations for both analytical and operational use cases, delivered in a much shorter timeframe than traditional data integration tools.

The Denodo Platform drives agility, faster time to market, increased customer engagement from single view of customer and operational efficiencies from real-time business intelligence and self-serviceability.
Founded in 1999, Denodo is privately held, with main offices in Palo Alto (CA), Madrid (Spain), Munich (Germany) and London (UK).

Denodo Customers

Autodesk, VHA, AAA, Sumitomo Mitsui Trust Bank, Caterpillar, European Chemical Agency, Seagate, Nationwide, Time Warner Cable, Pantex, Inditex, BNSF Railways, Vodafone, CIT Group, Jazztel, Wolters Kluwer, Telefonica, TransAlta

Denodo Video

Denodo Pricing Advice

What users are saying about Denodo pricing:
  • "Talking with my manager and others, nobody has complained about the pricing so far which is a positive sign."
  • "Denodo provides a lightweight 30-day free trial, but when we do courses on top of it, it costs $150 for each person."
  • "I am not super familiar with the pricing, but so far, it seems good. We have been happy. We haven't seen any problems. The only time we had to pay extra was during the upgrade. We didn't upgrade at the time they told us to upgrade, and we had to pay extra to keep the service. They had stopped the support for the older version and moved to the newer version. It was not their fault. It was our fault because we didn't get on board quickly."
  • "Depending on the size of the client you want to work with, it can be prohibitively expensive at times."
  • "For us, the cost has been okay. Also, there are no additional costs; it's just the standard licensing fee."
  • Denodo Reviews

    Filter by:
    Filter Reviews
    Industry
    Loading...
    Filter Unavailable
    Company Size
    Loading...
    Filter Unavailable
    Job Level
    Loading...
    Filter Unavailable
    Rating
    Loading...
    Filter Unavailable
    Considered
    Loading...
    Filter Unavailable
    Order by:
    Loading...
    • Date
    • Highest Rating
    • Lowest Rating
    • Review Length
    Search:
    Showingreviews based on the current filters. Reset all filters
    Dash Bibhuprasad - PeerSpot reviewer
    Lead Solution Architect at a insurance company with 10,001+ employees
    Real User
    Saves our underwriters' time with data virtualization, but could provide more learning resources
    Pros and Cons
    • "While we may not be using all the features of Denodo at this time, we have found the data virtualization features to be very useful in helping us connect our data sources together, bringing all our data into one platform."
    • "It would be beneficial to make sure that the team that will be using Denodo has some kind of training on how to use the product at least a month beforehand, and there could even be some kind of feedback or Q&A sessions to go along with the training. If Denodo were able to provide this kind of training, it would be very helpful to users in insurance and banking companies because the staff are typically older and not always technically-minded."

    What is our primary use case?

    I work with an insurance company and our main reason for using Denodo is to bring together all our data into one platform in the cloud. The company has very diverse data sources including data stored in the cloud, XML files, Db2 and SQL databases, and SAM / VSAM files on legacy mainframe platforms. Thus, management decided that they wanted all the data in one place by connecting these different data sources for better visualization and reporting.

    It's really working well for us and we are using it for both of our claims centers with our claims management solution as well as our premium management solution. One instance of Denodo is for the underwriting team and the other is for the actuary team. In total, we have around 45 people using it.

    We were originally using the solution on-premises but we are now using the cloud version deployed on Azure.

    How has it helped my organization?

    There are a lot of benefits of using Denodo in our company. Suppose, as an underwriter, you are approving a policy for a customer; typically, you will have to do a number of SQL queries or perform macros on Excel to find out information such as, "How many years has this customer been with the company and how is their claim history?" or "How is this customer's business actually doing?" There are many things that underwriters want to check before they approve any underwriting amount. And this means, for any approval, they're taking up to three or four hours, especially in a commercial insurance setting with all the changes that have taken place during Covid.

    Lots of companies have filed for bankruptcy or are not doing as well as they should be, so there are many changes that the underwriting teams have to take into account. These teams could be doing great business by writing the right amount for premiums for the company or for the client, and they have been having a lot of difficulties reaching certain data points in order to give their final verdict.

    However, now that everything is in front of them in one virtualized screen, they can quickly see all the necessary data such as claims files, history files with previous premium history, how much lifetime value the client has for the company, etc. They can obtain all these pieces of information from a single search and then make an appropriate decision to approve or deny, all within 15 to 20 minutes. Considering that the time to do such things has come down to 20 minutes from three hours, you can tell how much time has been saved by using Denodo.

    Also, some of the underwriters are over 60 years old, having been in the company for 35 years or more, and they don't love technology that much. Yet, with the training that we've given them, they're slowly starting to enjoy it and are now able to appreciate how much time it has saved them. They are very aware that Denodo is helping them, even though they would have been happy to stick with Excel.

    What is most valuable?

    We initially thought that we'd be using more features of Denodo than we are currently. And, in fact, there is a large number of features, ranging from data visualization to data virtualization and connecting to different non-connectable parameters (such as connecting to many different types of files, which other products don't allow you to do as easily as Denodo does). However, after we moved to the cloud with Azure, we mainly used only the data virtualization features of Denodo, while opting for Power BI when it comes to visualization with dashboards and reporting.

    So while we may not be using all the features of Denodo at this time, we have found the data virtualization features to be very useful in helping us connect our data sources together, bringing all our data into one platform.

    What needs improvement?

    As a company, we first did a proof-of-concept for about four months to make sure the product was a perfect fit for us or not, and beyond that I have only used Denodo for another year or so, so I know that we haven't used the product to its fullest yet. Indeed, a lot of Denodo has changed since we had our first presentation on it with the Denodo sales team who gave us a rundown of all the features. Nevertheless, there are multiple ideas I could suggest in terms of improvement.

    First of all, the visualization and reporting could be better. Of course, the data virtualization is good, but the data visualization could be improved with regards to the real-time dashboarding of the graphs, pie charts, etc. For the real-time data, the dashboard should preferably be updated automatically every hour. Let's say, as a CEO or CFO, I just want to know how much premium the company will get at any hour of the day. This data should be readily available on the dashboard. This is largely why we stick with Power BI's dashboarding features (besides the simple fact that Power BI works well hand-in-hand with Azure), and why we still haven't used Denodo's data visualization features as much as the data virtualization features. 

    Another area we have been struggling with is the integration of Denodo with both Salesforce and MuleSoft, which we use to track the customers in our sales system, such as when sending insurance quotes. When we first tried to integrate Salesforce, we found that there was some type of version incompatibility. We had a hard time talking with Salesforce about this, but eventually we upgraded our version and the integration was resolved. Yet, this was a challenge that I feel we didn't need to go through, as we were not able to quickly map out the issue. And with MuleSoft, we have not been able to integrate it properly at all.

    I have also seen our users complain about the availability of data sources, where they are sometimes not able to connect to all the sources they need. This kind of complaint, however, is difficult to diagnose, and I don't know for sure whether it is due to how we have Denodo set up in the company, or whether it's an actual issue with Denodo itself. These complaints were mainly made during the first few months of our usage, so it is possible that the problems stemmed from a lack of knowledge on how to use Denodo correctly, especially since the individual feedback would generally be something vague like, "Okay, I'm not able to do this". To help resolve these complaints, I would suggest that Denodo work on better documentation and perhaps some kind of virtual training.

    For example, there's an insurance software company called Guidewire, and when we first brought Guidewire into the company they sent us a lot of training videos even before the actual integration took place. For Denodo, it would be beneficial to make sure that the team that will be using it has some kind of training on how to use the product at least a month beforehand, and there could even be some kind of feedback or Q&A sessions to go along with the training. If Denodo were able to provide this kind of training, it would be very helpful to users in insurance and banking companies because the staff are typically older and not always technically-minded. They say, "You are pushing us too hard", so they need encouragement when it comes to adoption of a new software product.

    Buyer's Guide
    Denodo
    November 2022
    Learn what your peers think about Denodo. Get advice and tips from experienced pros sharing their opinions. Updated: November 2022.
    653,584 professionals have used our research since 2012.

    For how long have I used the solution?

    I have been working with Denodo for about two years now.

    What do I think about the stability of the solution?

    We don't have many complaints about the stability of Denodo. So far it's behaving well.

    What do I think about the scalability of the solution?

    Denodo is very scalable. That's the best part of it; you can add extra features and also integrate the product with other software.

    In terms of users, we have about 45 people working on Denodo, mostly simultaneously.

    How are customer service and support?

    The support, so far, is good. When opening tickets, there isn't a problem with response times, and there are no complaints from users internal to the company in this regard.

    Which solution did I use previously and why did I switch?

    With one of our main goals being to collect data through SQL, we have also done reporting with BO (Business Objects) and Cognos, which gets delivered to the operations team. However, before Denodo, I hadn't any experience with data virtualization, which is what we primarily use it for.

    One thing that I am happy about is that Denodo now has an API available. The development team can easily build on the API and expose it so that other teams can start using it. With this, we can take all data from different sources and put it in the cloud, and then from the cloud we can build our own product and perhaps even put our own dashboarding on top of that.

    It was actually one of the senior IT directors (who recently joined us from Infosys and has a lot of experience with financial clients) who recommended Denodo for our company. He really pushed us on it, emphasizing its cost-effectiveness, so my VP and team all agreed to go for the proof-of-concept. After doing the POC, we really liked the product and simply went for it.

    How was the initial setup?

    The deployment was good, but finding the right environment to deploy to isn't too easy. For every new product, we do an infrastructure assessment and we did the same for Denodo. Initially, it took some time to make it happen with all the approvals needed, but in terms of complexity, it wasn't too bad. I would rate the complexity of the deployment a 6/10.

    Our proof-of-concept took place over the course of about four months, and the POC version was very easy to handle since we got a lot of support from Denodo during that time. Their team was always talking to us and came in with two or three guys at a time. When someone is there helping you, backing you up, you feel comfortable. Of course, it took a bit of time to get all our staff on board, but it was easy enough.

    When we went with the full and final rehearsal, it actually took more time to work than expected to make everything ready. This took about two to three weeks for us, because we first needed the results from the security team, infrastructure team, payment team, and so on. There were many people involved in the deployment, both internally and externally, so it did take a while to get settled.

    What about the implementation team?

    We had both in-house teams and personnel from outside the company perform the complete implementation.

    What's my experience with pricing, setup cost, and licensing?

    The licensing is taken care of by the procurement team, but I think the pricing was good. I believe our company got a good discount on the market price for the first two or three years. After that, we are going to be paying in full.

    Talking with my manager and others, nobody has complained about the pricing so far which is a positive sign.

    What other advice do I have?

    Denodo is a good product with superior stability and scalability, and it can be very helpful to the various teams of a company in different ways. However, even though products like Denodo are a good choice for many buyers, you shouldn't forget to undergo the proper training and analysis on how to make the product most useful in your specific circumstances. You need to know your processes well, including your weaknesses and the particular challenges that your company needs to overcome. If you can cover these areas, you will find Denodo to be an excellent solution.

    I would rate Denodo a seven out of ten.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Microsoft Azure
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Naresh Maddineni - PeerSpot reviewer
    Senior Application Developer at a financial services firm with 10,001+ employees
    Real User
    Quick and simple web services creation, but needs better customizability and a fallback option
    Pros and Cons
    • "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)."
    • "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."

    What is our primary use case?

    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.

    How has it helped my organization?

    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.

    What is most valuable?

    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.

    What needs improvement?

    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.

    For how long have I used the solution?

    I have been using Denodo for one year now.

    What do I think about the stability of the solution?

    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.

    What do I think about the scalability of the solution?

    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. 

    How are customer service and support?

    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.

    Which solution did I use previously and why did I switch?

    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.

    How was the initial setup?

    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.

    What's my experience with pricing, setup cost, and licensing?

    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.

    What other advice do I have?

    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.

    Which deployment model are you using for this solution?

    Public Cloud
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Buyer's Guide
    Denodo
    November 2022
    Learn what your peers think about Denodo. Get advice and tips from experienced pros sharing their opinions. Updated: November 2022.
    653,584 professionals have used our research since 2012.
    Senior Manager Data Analytics at a recreational facilities/services company with 10,001+ employees
    Real User
    Top 20
    Allows us to be BI-tool agnostic, but there should be an easy way to export the data model
    Pros and Cons
    • "One thing that we have noticed is that when you have a BI tool, you end up building a lot of the logic in the BI tool, but as a company, every company wants to be tool agnostic because today, you could be in the Qlik Sense, and tomorrow, you may decide to go with Tableau or something else that is there. If you have put a lot of logic within the tool, transitioning or moving away from one BI tool to another tool becomes a very intensive process. By keeping the logic in Denodo, you can move to any tool."
    • "I would like it if we could pull the data model or export the data model because Denodo has, based on how you build, something called associations. The data model gets very confusing when you go look at it. It depends on how you define it, but it's really huge. I wish there was a way to export it into Visio. It could be that they already have a way to do it, and I don't know, but it would be much easier for the architects and even for the developers to look at it than scrunching it into the screen and expanding every small portion of it. If there was an easy way to export the Denodo model into another modeling tool and view it, it would be great."

    What is our primary use case?

    We are currently using it in our company, and it's our data virtualization tool. We fall under the federated analytical model. Basically, we have data that moves into our warehouse, and from the warehouse, when we want to build our reports, we use it. So, we are mainly using it for reporting purposes at this point. Instead of building aggregated views in our warehouse, we put that on the Denodo layer.

    We aggregate the data in our Denodo layer. Because Denodo is a virtualization tool, we try not to cache the data, but we've cached it whenever needed. Our dashboards usually run once a day or twice a day. So, we refresh the data once or twice a day. Sometimes, we also refresh every hour, but mostly, we refresh once or twice a day. For that, we don't need the data materialized in a view. We don't need the data to be there. We just create these views on Denodo. We have Power BI and Qlik Sense, and we just use those tools to pull the data from Denodo.

    There are other uses as well that we are thinking of as a company. We have business users who do want to look at the backend of what's going on. They may just want to run something like a quick analysis. For example, for a question, they just want to go take a look at the actual data. For that purpose, we can give these analysts access, and they can go in and take a look at that. Eventually, we want to go to a place where we want to enable self-service analytics for our business users. We are thinking that Denodo could help us in that direction. I know different companies use Denodo for different purposes, but we are using it on the IT side. Currently, we are using it mainly for reporting purposes, but we could also move towards self-service and make it available to our business users as well. That's for the future. We haven't done that yet. For now, we are only doing it at the BI layer.

    What is most valuable?

    One thing that we have noticed is that when you have a BI tool, you end up building a lot of the logic in the BI tool, but as a company, every company wants to be tool agnostic because today, you could be in the Qlik Sense, and tomorrow, you may decide to go with Tableau or something else that is there. If you have put a lot of logic within the tool, transitioning or moving away from one BI tool to another tool becomes a very intensive process. By keeping the logic in Denodo, you can move to any tool. That's what we have done at this point because we used to have Cognos in my company before. When we did the migration from Cognos to Power BI, it was quite intensive for us because a lot of the logic was sitting in SQL queries within Cognos. To move to Power BI, we had to do a lot of backward thinking. These reports were built more than 5 years ago, or even 10 years ago, and the people who built them were no longer with the company. The logic was pretty much gone. We didn't have good documentation, but now, after we have put the code in Denodo, we have visibility. Any developer, not a business analyst, can come and take a look at that code and discern how the data is moving from the warehouse to Denodo. All that Power BI or Qlik Sense is doing is just pulling the data from that view. We can do averages and other calculations in the tool, but at least our aggregation and the logic are in the Denodo layer, and then going forward, we can take it to any tool.

    Last year, they moved from version 7.0 to 8.0, and version 8.0 gives a lot of flexibility.

    What needs improvement?

    I would like it if we could pull the data model or export the data model because Denodo has, based on how you build, something called associations. The data model gets very confusing when you go look at it. It depends on how you define it, but it's really huge. I wish there was a way to export it into Visio. It could be that they already have a way to do it, and I don't know, but it would be much easier for the architects and even for the developers to look at it than scrunching it into the screen and expanding every small portion of it. If there was an easy way to export the Denodo model into another modeling tool and view it, it would be great.

    We are also trying to use Denodo as a cataloging tool so that we can put proper definitions, and once they are made available to our business users, it becomes easy. Using the Denodo layer, we can write queries to pull data. There is a virtualization layer. So, we can interact with it just like any other database. If there was a way to write a query and make my query public to other users so that they don't have to come in and write their queries, it would be great. There should be reusability of something that I did. For example, if I'm working in the healthcare industry and I want to get a view of the patient count for the whole year, I should be able to write a query and make it public so that whoever wants to use it can use that query instead of creating the same query again.

    For how long have I used the solution?

    I have been working with this solution for a little over three years.

    What do I think about the stability of the solution?

    It has been pretty stable. We've had some minor issues here and there, but we do have an admin who is assigned to this. We have a full-time paid Denodo admin. If there is a problem, he is very fast at getting onto the problem. He connects with Denodo and then comes back with solutions. Overall, we've had minor things here and there. Sometimes, we have to use certain Java functions to figure it out. There is also a learning curve for some people because not everybody knows Java coding.

    We recently upgraded to Denodo 8.0. We pushed the upgrade for a very long time because my team is the biggest consumer of Denodo. So, we had to look at our timelines to do it, but it was very smooth. Denodo helped us really well in the upgrade, and my team and our admins were also on top of everything. The whole Denodo 7.0 to 8.0 upgrade went smoothly. It went so smoothly that I just couldn’t believe it.

    What do I think about the scalability of the solution?

    So far, it has been good. We have between 50 to 100 users. It is used on a daily basis.

    How are customer service and support?

    I'm not super familiar with that mainly because our admin is the one who takes care of it, but he hasn't complained. So, their support should be okay, but it's hard to know how good or bad their support is because we have a full-time admin.

    Which solution did I use previously and why did I switch?

    I haven't used any other solution. I have used virtual data lakes. On Hadoop, I have used that. One thing that I felt is that there is a learning curve for Denodo. It's not something that people just start using. They can learn it, but it's going to take some time for them to get to know it. For example, if you know SQL, Oracle, or Teradata, the structure is pretty much the same, but I cannot have a developer come in and start working on Denodo from next week. It's not possible. They need some time.

    How was the initial setup?

    When I came to the company, the initial setup was already done. It was already there, but from what I have heard, Denodo has been very helpful with the initial setup. We did buy a package so that we get the initial help for setting up everything.

    What's my experience with pricing, setup cost, and licensing?

    I am not super familiar with the pricing, but so far, it seems good. We have been happy. We haven't seen any problems.

    The only time we had to pay extra was during the upgrade. We didn't upgrade at the time they told us to upgrade, and we had to pay extra to keep the service. They had stopped the support for the older version and moved to the newer version. It was not their fault. It was our fault because we didn't get on board quickly.

    What other advice do I have?

    There is a learning curve, and you would need at least two to three weeks. You can make it very complex, and you can make it very simple. I know different people do it in different ways. Ours was a little bit of a structured process, which could also be the reason why it takes some time for people. We don't just approve everything through Denodo. We have a review committee, and the review committee decides and approves or denies a new table or a new view. We have a review process. That's one of the things that has helped in keeping Denodo's environment clean.

    I would rate it a 7 out of 10. The reason is that in our company, we haven't explored everything that Denodo can offer. The tool is good, but we've only scratched the surface, and it may have additional functionalities that we haven't used. The more we use Denodo, the more we'll like it.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Alisson Machado De Menezes - PeerSpot reviewer
    Senior BigData DevOps Engineer at Schaeffler
    Real User
    Great for queries and scouting data but not scalable
    Pros and Cons
    • "In general, it's good for us to make tests so we can scout the data."
    • "The git configuration really should be improved."

    What is our primary use case?

    Currently, we are using it on Azure. We have around four VMs with Denodo divided into development, quality, and production environments. We have various configurations. I don't really work developing the queries on Denodo, it's more on the administration side. I have managed the scalability, the configurations, and providing the environment.

    Currently, we use Denodo mostly to query data from SAP. We have a very old SAP inside of Schaeffler that doesn't have encryption. To retrieve this data from other people, to use the same data, we use Denodo to make this encryption. Then we have a few databases, and we can create base views based on the SAP tables. 

    In some use cases, they also create web services based on these tables as well. They use it a bit as an ETL tool. They use for data scouting. For example, we have one tool that was developed inside of Schaeffler called Discovery, where we used Denodo to get the metadata from basically all the different systems that we have.

    How has it helped my organization?

    It's been useful to have the same language to query manager-friendly databases. That would be the main benefit. The second one is that we can create web services without any programming based on the base use that we create on Denodo. 

    What is most valuable?

    Getting queries is great. They are really good. You can basically write SQL statements, and it can convert to MDX queries or to MongoDB queries, or any kind of data source. We have many different data sources. You just use the requisite language, which translates to all the underlying data sources. That's the best thing that we have on Denodo.

    In general, it's good for us to make tests so we can scout the data. We can make POCs easily. 

    What needs improvement?

    It's not really scalable. We have a couple of problems with a high demand for the servers. It also doesn't have very good integration with Git, so it's not possible to work with branches with the developers. When it goes to production, then we cannot use it anymore.

    The git configuration really should be improved. It would help a lot. Then the developers could have different values of the same project and use, for example, GitFlow for the projects. That would be amazing. If they had it, the scalability would be very good. And we can actually have one external metadata database for starting the Denodo configuration. However, it's very slow. 

    If it were possible to work around Kubernetes, for example, it would help. They have some implementations. However, it doesn't really work as expected.

    The solution is expensive as you are charged by the CPU. 

    For how long have I used the solution?

    I've been using the solution for three years. 

    What do I think about the stability of the solution?

    For production the stability is okay since we don't have a lot of things going on. In production, we have a couple of years of use cases. Of course, there is a high demand for CPU and memory. However, in development, we have a lot of issues based on the problems we've had with the Git integration. There are a lot of conflicts, there are a lot of problems.  

    If you have just the applications pointing to Denodo and running the specific query, it's okay.

    What do I think about the scalability of the solution?

    The solution does not scale well at this time. 

    We have a lot of users. They don't do the deployments. However, they do development in the development environment, of course. I would say we probably have 100 users.

    How are customer service and support?

    I don't like the support. They always blame the customer. For example, sometimes we have some bugs on Denodo and open a ticket. They ask you to run thousands of tests to ensure that it's not a bug, however, in the end, it is a bug, and we knew since the beginning. Sometimes it takes a week for them to say, "Yeah, okay, it's really a bug." 

    Then, God knows when they will give an update as they have one voting system at the service desk. Other customers need to vote on the same bug or the same feature that you requested, and then it will go in the next release. 

    It's very hard, for example, to have a call with them. It's very hard to get support when it's a problem with the tool. They always say that the customer doesn't know how to use the tool and it's not so nice.

    Which solution did I use previously and why did I switch?

    I was in touch with a company called Starburst and CData. They seem to do nearly the same stuff. We just had to try the tool, to install and try to run the same things on Denodo. I didn't really have time for that, so I cannot say a lot. However, it could be an alternative.

    How was the initial setup?

    It's very easy to set up the product. We have the solution manager on Denodo, so you can basically create a revision. Suppose you have the database from one environment, for example, from development. In that case, it will generate basically a backup, and it will deploy this backup in the other servers that you want.

    We have three people that handle the implementation and deployment. It's me and two students in my team who are learning how to do this stuff. We basically have three DevOps engineers who are in charge of that.

    The deployment of Denodo is very quick. It takes less than a minute.

    In terms of maintenance, usually, we don't have many problems. Sometimes we face issues with credentials, however, the procedure that we need to establish is not yet well-defined. That said, usually, in production, we hardly ever have problems.

    What's my experience with pricing, setup cost, and licensing?

    I don't have details of how much it costs, however, it's expensive. 

    You pay per CPU. If I have 10 CPUs or 12 CPUs, it increases the price.

    What other advice do I have?

    We're a customer and end-user.

    We're using the latest version.

    We have a contract until the end of 2023. Then, maybe after that, we won't want to keep this technology. That said, we don't have any replacements so far. We have to run some POCs and tests and plan a migration since we have around 46 use cases on top of Denodo. It needs to be planned if we decide to switch.

    A potential new user should run a lot of tests before they pay a license. For example, try the support and see if the relationship works. There are some customers that are very happy. We have not been as lucky. Some are very happy, some of them they are not so happy. It depends on what your usage will be.

    I'd rate the solution seven out of ten.

    Which deployment model are you using for this solution?

    Public Cloud
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    LeandroSodré - PeerSpot reviewer
    Data Governance Analyst at Data Meaning, Inc.
    Real User
    Top 5
    Powerful, features, has the ability to connect to multiple data sources, and the technical support is helpful
    Pros and Cons
    • "The most valuable aspects of this solution are the short time frame in which you can deliver and connect."
    • "The feature that you have to connect on LDAP needs improvement."

    What is our primary use case?

    We use Denodo to improve data governance and self-service BI.

    We had several data environments, one data lake, one data warehouse, and another instance of data in another silo, and we needed to deliver this data to our end users in an organized manner.

    It was very, powerful because we could deliver this data in a short time and with some data governance, because you deliver it through a data catalog and you have the data lineage, and you can put there the role level security, column level security, and it was very helpful for us, and the end-user was very happy to have it.

    What is most valuable?

    The most valuable aspects of this solution are the short time frame in which you can deliver and connect.

    I don't have a single feature because I believe the ability to connect disparate data sources is extremely useful. 

    You can create a layer over these various data sources and deliver the data to the end user as a single data source. This, I believe, is the most powerful feature in Denodo, because it is data virtualization.

    Consuming metadata from pipelines is something that would most likely be interesting. If we could integrate it, for example, with some ODI or some Data Factory, because if you have this, you might be able to take advantage of the work that the tech engineer has already done, and you might be able to turn Denodo into a more powerful solution because it can be used for more than just data virtualization.

    What needs improvement?

    The feature that you have to connect on LDAP needs improvement.

    I am not sure if it's on Denodo's side, but sometimes it is very difficult to connect on LDAP, and you can take advantage of this by using the roles that have already been created there.

    I have no complaints about Denodo's features, except perhaps the price.

    For how long have I used the solution?

    I have been using Denodo for approximately one and a half years.

    I no longer use it, but when I did, I started with version 7 and by the end of the semester, I was using version 8.

    It was deployed both on-premises and on the Cloud.

    In one company, I use on-premise, and when I worked at a consulting firm, I assisted in deploying a cloud environment for our clients.

    What do I think about the stability of the solution?

    Denodo is a stable solution.

    Version 8 is much more stable than version 7.

    What do I think about the scalability of the solution?

    Denodo is scalable.

    We had approximately 1,000 users.

    I no longer work for the same company. However, as a consultant, I always try to bring it to my manager in order to sell it to our clients, because as someone who works with data governance, I believe Denodo is a powerful tool for reducing the time it takes to implement data governance while also providing organized self-service BI.

    How are customer service and support?

    The technical support is great.

    I would rate them a five out of five.

    Which solution did I use previously and why did I switch?

    Previously, we used Dremio, which was the only solution that allowed us to use it for free due to its open-source nature. We tried Dremio, and during the PoC, we didn't try any other tool, but we could see some presentations about Data Virtuality, which is a German company if I'm not mistaken.

    How was the initial setup?

    It was a pleasant surprise to discover how simple it is to set up this environment.

    We have a development team of five to maintain this solution.

    What about the implementation team?

    When doing the PoC, we did use the consultant.

    When we went to production to deploy on our side, we did it ourselves, with Denodo's help, because it was included in our license.

    What was our ROI?

    Yes, we saw a return on investment.

    What's my experience with pricing, setup cost, and licensing?

    Depending on the size of the client you want to work with, it can be prohibitively expensive at times.

    I am not sure how much it costs right now, but we did the PoC to justify purchasing the solution. It was approximately 1 million reais.

    What other advice do I have?

    I would say that it is critical that you have some business model built, because it will guide you on how to implement the data sets in Denodo because you need to consume several data sources, but you must put them in some way that has some meaning to the business, you must migrate from physical modeling to logical modeling and business modeling. 

    I would say you should incorporate these three layers into Denodo. To take advantage of Denodo, you must consider these three layers. Otherwise, you will just put some data there and no one will find it.

    I would rate Denodo an eight out of ten.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Tech Lead and Architect at SEI
    Real User
    Top 10
    Can fetch and write data simultaneously, but the conversion of date and number formats needs improvement
    Pros and Cons
    • "In PL/SQL, first you need to gather all the data and then start writing the file, but in Denodo you fetch the data and write the data simultaneously. So, for example, if you have 1 million or 2 million records, you don't have to wait to fetch all of the 2 million; you can keep on fetching and writing in the file simultaneously."
    • "Tasks such as conversion of a date format or conversion of a number format that can be done in a very easy way in different languages, like SQL or Oracle, are not so easy to do in Denodo. For example, if you want to convert a date from one format to another, in Oracle it's pretty easy; in Denodo, however, it requires so many lines of code. Simple things that can be done very quickly in other database languages require more lines of code in Denodo."

    What is our primary use case?

    I work for a company that provides financial solutions to banks and advisors. We need to send data everyday to different third parties in different file formats, like pipe delimited, comma separated, fixed width, xml, etc. Previously, we used to generate those files with the data using PL/SQL. After looking at the performance issues and the complexity, we started using Denodo.

    We run scheduler jobs in Denodo, and the job will in turn run the VQLs. VQLs will gather the data based on the business rules and business logic. Finally, it will spool the data in a predefined file format, and then the file will be delivered to the respective recipient. Basically, we generate interfaces using Denodo.

    What is most valuable?

    Caching was very valuable to us.

    In PL/SQL, first you need to gather all the data and then start writing the file, but in Denodo you fetch the data and write the data simultaneously. So, for example, if you have 1 million or 2 million records, you don't have to wait to fetch all of the 2 million; you can keep on fetching and writing in the file simultaneously.

    What needs improvement?

    Tasks such as conversion of a date format or conversion of a number format that can be done in a very easy way in different languages, like SQL or Oracle, are not so easy to do in Denodo.

    For example, if you want to convert a date from one format to another, in Oracle it's pretty easy; in Denodo, however, it requires so many lines of code. Simple things that can be done very quickly in other database languages require more lines of code in Denodo.

    The scheduler UI in 8.0 is not as good as that in 7.0. We have thousands of jobs, and if you search one job, get it, and click on it, when you come back, your search will be gone. You have to do your search all over again. The 7.0 UI was much better.

    For how long have I used the solution?

    We have been using Denodo from the last quarter of 2018.

    Right now, it's deployed on-premises, but in the next few months, we are planning to move it to the cloud.

    What do I think about the scalability of the solution?

    It is scalable.

    We have three administrators and about 20 to 25 developers working on this tool.

    How are customer service and support?

    We have biweekly meetings with Denodo staff. Apart from that, whenever we have any issues or concerns, we just raise the ticket on the Denodo portal, and we get a response. The technical support is good.

    How was the initial setup?

    The initial setup was okay for us and was not complicated. We created a couple of virtual machines; we got a 4-core license. We installed two VMs, and one was always active. The second one was always down. Whenever we needed the second one, we brought it up. Otherwise, we mainly worked on one VM.

    Once the VMs and all the machines and infrastructure were ready, the installation and setting up of all the configurations took two to three days maximum to complete.

    For maintenance, we have three persons, two on-site in the US and one offshore.

    What about the implementation team?

    We deployed Denodo ourselves.

    What was our ROI?

    Before Denodo, our interfaces were running for six to seven hours to generate a file. After writing the same thing in Denodo, now those interfaces are generated in 25 to 30 minutes. So for us, we came down from seven hours to 30 minutes, and that is our ROI.

    What's my experience with pricing, setup cost, and licensing?

    For us, the cost has been okay. Also, there are no additional costs; it's just the standard licensing fee.

    What other advice do I have?

    First, understand your use case properly, and then analyze the tool and see whether or not the tool is going to perfectly fit your use case. Denodo is mainly for data virtualization, though it has the functionality to create files and write data in the files. However, given my four years of experience that is not the best use case for Denodo. For data virtualization and fetching data from multiple systems and data sources though, Denodo is a good tool.

    I rate Denodo at six on a scale from one to ten.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    AbhijeetKarki - PeerSpot reviewer
    Data Solutions Architect at Cognizant
    Real User
    Connects and integrates well to many different sources; lacking in performance management
    Pros and Cons
    • "The ability to connect to a lot of different sources."
    • "Performance management could be improved."

    What is our primary use case?

    We use this solution as an access layer and virtualization layer. We connect to a number of sources and then use Denodo as the main access layer for consumers or for reporting. I have also personally used it for integrating sources for some of our critical reports which was a use case outside the regular virtualization capability. We calculated some of the key metrics for our critical components. I'm a data solutions architect and we are partners with Denodo. 

    What is most valuable?

    The strength of Denodo is that we can connect to a lot of different sources; it easily integrates and directly connects. It's great that it can flatten a JSON file and present connectors with a view format for downstream consumers. I would say reading or connecting to various sources and presenting a tabular view is an awesome capability. It can also be done with PDFs. The product has a good technical data catalog. 

    What needs improvement?

    I think Denodo needs a bit of work with performance management. When data sets are huge and a heavy query has been pushed out to the database, it can take quite some time to get what you need without clear optimization techniques. It requires clearer instructions. Some features should be added on the performance management and optimization side of things. I'd like to see them provide more on data governance. In addition, it would be good to have some support for analytical queries in SQL as that can be a challenge at times. There is currently no advanced analytic support for the SQLs.

    For how long have I used the solution?

    I've been using this solution for two years. 

    What do I think about the stability of the solution?

    Denodo as a platform is stable overall. It can be a challenge if there are hundreds of users running a lot of queries, and then one of the queries suddenly sucks up the resources. When that happens, the system fails and there can be a risk to the source. 

    What do I think about the scalability of the solution?

    If you have the product on the cloud, it's easily scalable. The risk is that because Denodo connects itself to some source databases, if there are multiple users,  then fired queries are delegated to the source which is a risk to the source. Denodo itself can scale up or down if it's on the cloud. We have close to 100 users on a daily basis. 

    How are customer service and support?

    We have a separate operations team but I have connected with Denodo support and they were helpful. They were knowledgeable about the product. We were able to directly interact with their technical teams. So anytime we raised a ticket, we got a fairly quick reply and they were able to resolve the issue promptly. In the early days, our operations team connected with the Denodo technical team once a week to run over any issues. They were quite helpful with that.

    Which solution did I use previously and why did I switch?

    We also use DBT, which is a data build tool with a similar function in terms of creating views on SQLs and then deploying on Snowflake. Both DBT and Denodo are popular because both of them are heavily SQL-based. If you only use Snowflake, DBT is preferable to Denodo. But if you're integrating data from different sources, Denodo is likely preferable.

    How was the initial setup?

    I wasn't involved with the company's implementation. Deployment was pretty straightforward when I implemented it on my laptop. There wasn't much to it; you install it, and it starts working.

    What's my experience with pricing, setup cost, and licensing?

    This is an expensive solution although I'm unsure exactly what our licensing costs are. Denodo is set up in nodes and each node is extremely costly. 

    What other advice do I have?

    We're still trying to find a place for Denodo within the organization's architecture. If you have a very clear use case, it's a good product. In terms of data virtualization, I think it's very well-rounded.

    I rate this solution seven out of 10. 

    Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
    Flag as inappropriate
    PeerSpot user
    Data Analytics Specialist at a pharma/biotech company with 10,001+ employees
    Real User
    Top 5Leaderboard
    Good performance and integration, but needs more training documentation
    Pros and Cons
    • "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."

    What is our primary use case?

    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. 

    What is most valuable?

    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. 

    What needs improvement?

    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. 

    For how long have I used the solution?

    I have been using Denodo for almost six months. 

    What do I think about the stability of the solution?

    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. 

    What do I think about the scalability of the solution?

    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. 

    How are customer service and support?

    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. 

    Which solution did I use previously and why did I switch?

    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. 

    How was the initial setup?

    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. 

    What about the implementation team?

    I implemented through an in-house team. 

    What other advice do I have?

    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. 

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user