Cloudera Data Science Workbench enables secure self-service data science for the enterprise. It is a collaborative environment where developers can work with a variety of libraries and frameworks.
N/A
Google App Engine
Score 8.2 out of 10
N/A
Google App Engine is Google Cloud's platform-as-a-service offering. It features pay-per-use pricing and support for a broad array of programming languages.
$0.05
Per Hour Per Instance
Pricing
Cloudera Data Science Workbench
Google App Engine
Editions & Modules
No answers on this topic
Starting Price
$0.05
Per Hour Per Instance
Max Price
$0.30
Per Hour Per Instance
Offerings
Pricing Offerings
Data Science Workbench
Google App Engine
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Cloudera Data Science Workbench
Google App Engine
Features
Cloudera Data Science Workbench
Google App Engine
Platform Connectivity
Comparison of Platform Connectivity features of Product A and Product B
Cloudera Data Science Workbench
7.5
2 Ratings
11% below category average
Google App Engine
-
Ratings
Connect to Multiple Data Sources
7.02 Ratings
00 Ratings
Extend Existing Data Sources
8.02 Ratings
00 Ratings
Automatic Data Format Detection
7.02 Ratings
00 Ratings
MDM Integration
8.02 Ratings
00 Ratings
Data Exploration
Comparison of Data Exploration features of Product A and Product B
Cloudera Data Science Workbench
7.6
2 Ratings
11% below category average
Google App Engine
-
Ratings
Visualization
7.12 Ratings
00 Ratings
Interactive Data Analysis
8.02 Ratings
00 Ratings
Data Preparation
Comparison of Data Preparation features of Product A and Product B
Cloudera Data Science Workbench
7.8
2 Ratings
5% below category average
Google App Engine
-
Ratings
Interactive Data Cleaning and Enrichment
7.02 Ratings
00 Ratings
Data Transformations
8.02 Ratings
00 Ratings
Data Encryption
8.02 Ratings
00 Ratings
Built-in Processors
8.02 Ratings
00 Ratings
Platform Data Modeling
Comparison of Platform Data Modeling features of Product A and Product B
Cloudera Data Science Workbench
7.6
2 Ratings
10% below category average
Google App Engine
-
Ratings
Multiple Model Development Languages and Tools
8.02 Ratings
00 Ratings
Automated Machine Learning
7.01 Ratings
00 Ratings
Single platform for multiple model development
7.12 Ratings
00 Ratings
Self-Service Model Delivery
8.12 Ratings
00 Ratings
Model Deployment
Comparison of Model Deployment features of Product A and Product B
Cloudera Data Science Workbench
8.0
2 Ratings
6% below category average
Google App Engine
-
Ratings
Flexible Model Publishing Options
8.12 Ratings
00 Ratings
Security, Governance, and Cost Controls
7.82 Ratings
00 Ratings
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
Organizations which already implemented on-premise Hadoop based Cloudera Data Platform (CDH) for their Big Data warehouse architecture will definitely get more value from seamless integration of Cloudera Data Science Workbench (CDSW) with their existing CDH Platform. However, for organizations with hybrid (cloud and on-premise) data platform without prior implementation of CDH, implementing CDSW can be a challenge technically and financially.
App Engine is such a good resource for our team both internally and externally. You have complete control over your app, how it runs, when it runs, and more while Google handles the back-end, scaling, orchestration, and so on. If you are serving a tool, system, or web page, it's perfect. If you are serving something back-end, like an automation or ETL workflow, you should be a little considerate or careful with how you are structuring that job. For instance, the Standard environment in Google App Engine will present you with a resource limit for your server calls. If your operations are known to take longer than, say, 10 minutes or so, you may be better off moving to the Flexible environment (which may be a little more expensive but certainly a little more powerful and a little less limited) or even moving that workflow to something like Google Compute Engine or another managed service.
There is a slight learning curve to getting used to code on Google App Engine.
Google Cloud Datastore is Google's NoSQL database in the cloud that your applications can use. NoSQL databases, by design, cannot give handle complex queries on the data. This means that sometimes you need to think carefully about your data structures - so that you can get the results you need in your code.
Setting up billing is a little annoying. It does not seem to save billing information to your account so you can re-use the same information across different Cloud projects. Each project requires you to re-enter all your billing information (if required)
App Engine is a solid choice for deployments to Google Cloud Platform that do not want to move entirely to a Kubernetes-based container architecture using a different Google product. For rapid prototyping of new applications and fairly straightforward web application deployments, we'll continue to leverage the capabilities that App Engine affords us.
I had to revisit the UI after a year of just setting up and forgetting. The UI got some improvements but the amount of navigation we have to go through to setup a new app has increased but also got easier to setup. Gemini now is integrated and make getting answers faster
Cloudera Data Science Workbench has excellence online resources support such as documentation and examples. On top of that the enterprise license also comes with SLA on opening a ticket to Cloudera Services and support for complaint handling and troubleshooting by email or through a phone call. On top of that it also offers additional paid training services.
Good amount of documentation available for Google App Engine and in general there is large developer community around Google App Engine and other products it interacts with. Lastly, Google support is great in general. No issues so far with them.
Both the tools have similar features and have made it pretty easy to install/deploy/use. Depending on your existing platform (Cloudera vs. Azure) you need to pick the Workbench. Another observation is that Cloudera has better support where you can get feedback on your questions pretty fast (unlike MS). As its a new product, I expect MS to be more efficient in handling customers questions.
We were on another much smaller cloud provider and decided to make the switch for several reasons - stability, breadth of services, and security. In reviewing options, GCP provided the best mixtures of meeting our needs while also balancing the overall cost of the service as compared to the other major players in Azure and AWS.
Effective integration to other java based frameworks.
Time to market is very quick. Build, test, deploy and use.
The GAE Whitelist for java is an important resource to know what works and what does not. So use it. It would also be nice for Google to expand on items that are allowed on GAE platform.