You can translate the question and the replies:

Denodo on Cloud

Hi Team, We would like to know denodo configuration when it is on Cloud . Our Data soure would be relational MPP and Big Data ( Hadoop ) and downstream reporting tool will be Tableau/Google Studio 360/Cloud Data labs. In this case what would be the configuration in terms of OS, Database or Virtual CPU, RAM, Storage etc . Also can you please let us know will dendod can communicate with /Google Studio 360/Cloud Data labs? Also does Denodo can communicate with Amazon Redshift when it is on cloud? Let us know in case you need any more details from our end.
31-03-2017 08:56:20 -0400

1 Answer

Hi, Denodo has been successfully deployed in both on premise and cloud environments. Denodo always tries to push down processing to the data sources avoiding unnecessary, expensive data movement through the network. In that sense, there should not be too much difference in where the Denodo server is installed. But, when data from two or more data sources must be combined, moving certain amount of data through the wire is unavoidable. The decision of where to deploy Denodo will depend on the volume to be moved, and, in turn, it will depend on the use case. With that said, as a general recommendation, it is a good practice to install Denodo closer to where most of the data reside. To support complex environments with highly distributed data, a multilayered deployment would be recommended. Denodo-to-Denodo connections allow costly combinations be delegated to local instances avoiding unnecessary, expensive data movement. Starting in Denodo 6.0, Denodo has extended his offering with a new Denodo Platform for AWS/Azure that can be deployed directly from AWS/Azure Marketplace. Leveraging Amazon/Azure’s flexible rent-by-the-hour licensing, this licensing comes with a wide range of pricing options including number of data sources and volume of concurrent queries and results. Denodo Platform for AWS/Azure offers the same features as the on-premise version. As cloud deployment considerations: - Cloud subscription pricing in not economical for large deployments - Network latency has to be considered - Put Denodo Platform near your main data sources - Select the right AWS region - Combine Denodo on premise for local data sources with Denodo Platform for AWS for cloud-based data - The cache should be in the same location of the Denodo server Regarding the connections with Tableau/Google Studio 360/Cloud Data Labs: We are partners with Tableau and they support a built-in Denodo connector after the 10.4 version. For other versions we are commonly accesed through ODBC. Google Studio 360 doesn't support a generic ODBC/JDBC connector (9/8/2017), but you can read data from Denodo exporting the results as CSV. They are aware of their lack of compatibility for most databases and they suggest to use Google Sheets to import and transform the data (for a small amount of data). In Cloud Data Labs you can provide access to our data using any library in python made for this purpose ('pyodbc' for ODBC connections). Hope this helps!
Denodo Team
08-09-2017 10:47:40 -0400
You must sign in to add an answer. If you do not have an account, you can register here