What advice do you have for others considering Denodo?

End users of Denodo will mostly be non-technical, as they will query the system in plain English for data insights. I'd rate the solution nine out of ten.

If customers want to make their data valuable, they must know which data they are using. By using Denodo's data category feature, they can identify and manage valuable data effectively. I'd rate the solution eight out of ten.

The main motivation was their use of multiple technologies such as SQL servers and Oracle, spanning nearly twenty-five different databases. This multitude of data sources and information spread across various databases necessitated robust data integration and visualization capabilities. Denodo played a crucial role in enabling the bank to unify and visualize information from these disparate schemas and technologies. This achievement significantly enhanced their ability to derive comprehensive insights from the diverse datasets. Numerous insights and use cases have already been successfully implemented across various departments within the bank. These initiatives have encompassed areas like predictive analytics, customer behavior analysis, and the development of machine learning models for HR and revenue forecasting. Denodo's products help reduce time to market for new products and promotions, ensuring they reach customers promptly. This prevents revenue loss, especially at the customer and complaint levels, among other benefits. Denodo has three layers of security. It is integrated with Active Directory for authentication. It supports single sign-on within the organization, particularly in the banking sector, where it is a leader. This integration allows for auditing and monitoring of all staff members. This forms the first layer of security. The second layer involves fine-grained access control over specific tables, views, and even columns. Denodo provides specific controls to determine who can access which tables and columns at a granular level. The third layer consists of generic governance rules governing user groups such as development, operations, and administration teams. For instance, developers may have read-write access, administrators have full administrative privileges, and operations staff have predefined access rights. These rules govern the authorization and authentication processes within Denodo. Denodo is not an expert in AI nor does it propose AI-specific use cases. However, its abstraction layer can inspire ideas related to AI, such as predictive analytics for customer behavior, complaints analysis, churn prediction, forecasting future revenue trends, and identifying new customer benefits for a bank's portfolio, for example. It provide a six-month warranty post-production, followed by five years of product support. This includes updates, new batches, upgrades, and more. One admin and two development team are required for maintainance. Overall, I rate the solution a nine out of ten.

We connect all the data sources with Denodo, and Denodo connects with the metadata. We do not move the data. We embrace the fact that data now resides in distributed data sources. Through the metadata, we create a catalog. The catalog pretty much centralizes all our data management. Through the catalog, all the information is standardized. We can visualize the information, manipulate the data, and integrate the catalog with data-consuming systems like Power BI, Tableau, and Apache. We do not centralize data. People think we need to get all the data outside the sources and put it in a repository to manage data properly. It is not necessary. We can integrate and create the catalog without replicating or moving any data. We can integrate with all the data-consuming systems we have and create a logical data layer. Overall, I rate the solution a nine out of ten.

Denodo has streamlined data integration from multiple sources, such as various databases offered by Salesforce or PeopleSoft. The tool helps with big data analytics or cloud integration processes since I use it to create views from various sources, and on top of it, I also make dashboards. I work as a third-party or outsourced consultant in a company in India, and my team works in the USA, where Denodo is available in the service. In my company, there are around 70 people working with the product. The performance and scalability of the product are nice. I only face issues with the analytical functions since they don't work properly for SQL. I rate the product's UI an eight out of ten. If a company has to deal with multiple data sources, then Denodo can be used for virtualization. I rate the overall tool a ten out of ten.

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.

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.

I rate this solution an eight out of ten.

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.

I would rate Denodo seven out of ten.

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.

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.

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'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.

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.

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.

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.

Deonodo is Virtualization for Logical Data Warehouse but is not a full ETL solution. You can use it if your dataset doesn't require that much ETL cleansing. On top of that, if you want to quickly show your data and use your data for analytical purposes, then this is the best tool. We can connect to data sources on the go and can perform data privacy, data governance, etc. This is the best tool compared to other similar tools available on market. On a scale from one to ten, I would rate it at eight.

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.

Denodo is an easy tool that can be used for data mining. You can connect to all of the data sources. You can see the views easily. A beginner may find installation complex as he will have to configure the scheduler, the VDP client, and the audit as well. However, it will be fine for an experienced person. Overall, on a scale from one to ten, I would give Denodo an eight.

I would rate this solution a seven out of ten.

I rate Denodo a seven out of ten.

I would rate Denodo a 7 out of 10 for what they are offering. I recommend Denodo for use because it is easy to use, even for non-technical people who have some knowledge of data tables including Excel.

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.

I rate this solution an eight out of 10.

My advice for anybody who is considering Denodo is to investigate it first. Download a free copy from the AWS Marketplace and really test it before you embark on your projects. Ensure that it meets your requirements, no just in the short-term, but in the long-term. This is one of the better products on the market. I would rate this solution a seven out of ten.

They're an industry leader for an emergent layer, and they don't sell you everything else associated with it. There are not very many competitors. I would suggest to get on with the proof of concept with it, and then if it doesn't work, you can back away from it with very little pain. You can scale up and get on with it. We have found that all of the competitors have a series of products that would cost a great deal more. I just became a partner as a consultant. I went through the partner training very recently. I would rate this solution an eight out of ten.

We are local partners. We have a business relationship with Denodo. We would recommend the product overall. On a scale from one to ten, I'd rate it at an eight. If they improved their integration capabilities and used some standard integration interfaces, I would mark them higher. If they offered more training and support, I'd mark them higher still.

I haven't used a similar tool so I can't compare it to anything. I think it's a good product, despite some minor issues. I would rate this solution an eight out of 10.

My advice to someone considering this solution would be to understand your own personalized environment and out of the box configuration settings of Denodo. Our next journey would be to the cloud. That was the only thing that we were looking at embarking upon, but obviously, within a big corporation, we need to do due diligence from our side. I think Denodo had already the features to be integrated into the cloud we needed to do our homework to make sure that we could onboard the cloud with certainty. I would rate Denodo an eight out of ten.

I'm a consultant with a reseller. We use the on-premises deployment model. If clients are looking into integrating value sources and they don't have to be on the MPP clusters then I'd recommend Denodo. However, if they are looking at something more contained within the Data Lake construction, they should go for something more granular. I'd rate the solution nine out of ten.

If you have the business needs for data visualization which is a core technology that Denodo represents, then, I would say to go for it as the platform really works well. Don't have too high expectations on data catalog functionality. It works, but, its current implementation is rather rudimental. I would recommend it to others. For us, it is a success story. I would rate it a nine out of ten. Not a ten only because I am hesitant to give a perfect score.