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.

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.

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.

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.

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.

We bought both TIBCO Data Virtualization and Denodo. TIBCO is a strong product and was good, but the cost was an issue. The cost was the main factor and resourcing and support also came into the picture. TIBCO did not have much of a global presence. Given Denodo's licensing model, support, and market value, they opted to go with it.

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. 

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.

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.

I used SSIS as an ETL tool and some IBM staging tools, but not extensively.

I used SSIS at my previous company and then switched to Denodo here.

The time to market is significantly faster with Denodo, both for deployment and publishing updates. Additionally, the web service capabilities are fantastic. We can deploy any web service in just minutes without complex development or security concerns.

We had used ETL tools previously to move data and then export the data. 

We have worked with lots of other tools that do different things, but not data virtualization.

Net new. 

We didn't have any other data virtualization tools available. Denodo was one of our first options when we were evaluating solutions and luckily we were able to close a deal at a reasonable price level.