Amazon Tensor Flow vs. Databricks Lakehouse Platform

A well-suited scenario for using AWS Tensor Flow is when having a project with a geographically dispersed team, a client overseas and large data to use for training. AWS Tensor Flow is less appropriate when working for clients in regions where it hasn't been allowed yet for use. Since smaller clients are in regions where AWS Tensor Flow hasn't been allowed for use, and those clients traditionally don't have enough hardware, this situation deters a wider use of the tool.

Incentivized

If you need a managed big data megastore, which has native integration with highly optimized Apache Spark Engine and native integration with MLflow, go for Databricks Lakehouse Platform. The Databricks Lakehouse Platform is a breeze to use and analytics capabilities are supported out of the box. You will find it a bit difficult to manage code in notebooks but you will get used to it soon.

Incentivized

• Amazon Elastic Compute Cloud (EC2) allows resizable compute capacity in the cloud, providing the necessary elasticity to provide services for both, small and medium-sized businesses.
• Tensor Flow allows us to train our models much faster than in our on-premise equipment.
• Most of the pre-trained models are easy to adapt to our clients' needs.

Incentivized

• Process raw data in One Lake (S3) env to relational tables and views
• Share notebooks with our business analysts so that they can use the queries and generate value out of the data
• Try out PySpark and Spark SQL queries on raw data before using them in our Spark jobs
• Modern day ETL operations made easy using Databricks. Provide access mechanism for different set of customers

Incentivized

• SageMaker isn't available in all regions. This is complicated for some clients overseas.
• For larger instances, when using a GPU, it takes a while to talk to a customer service representative to ask for a limit increase. Given this, it's recommendable to ask in advance for a limit increase in more expensive and larger cases; otherwise, SageMaker will set the limit to zero by default.
• Since the data has to be stored in S3 and copied to training, it doesn't allow to test and debug locally. Therefore, we have to wait a lot to check everything after every trail.

Incentivized

• Connect my local code in Visual code to my Databricks Lakehouse Platform cluster so I can run the code on the cluster. The old databricks-connect approach has many bugs and is hard to set up. The new Databricks Lakehouse Platform extension on Visual Code, doesn't allow the developers to debug their code line by line (only we can run the code).
• Maybe have a specific Databricks Lakehouse Platform IDE that can be used by Databricks Lakehouse Platform users to develop locally.
• Visualization in MLFLOW experiment can be enhanced

Incentivized

Because it is an amazing platform for designing experiments and delivering a deep dive analysis that requires execution of highly complex queries, as well as it allows to share the information and insights across the company with their shared workspaces, while keeping it secured.

in terms of graph generation and interaction it could improve their UI and UX

Incentivized

One of the best customer and technology support that I have ever experienced in my career. You pay for what you get and you get the Rolls Royce. It reminds me of the customer support of SAS in the 2000s when the tools were reaching some limits and their engineer wanted to know more about what we were doing, long before "data science" was even a name. Databricks truly embraces the partnership with their customer and help them on any given challenge.

Microsoft Azure is better than Amazon Tensor Flow because it provides easier and pre-built capabilities such as Anomaly Detection, Recommendation, and Ranking. AWS is better than IBM Watson ML Studio because it has direct and prebuilt clustering capabilities AWS, like IBM Watson ML Studio, has powerful built-in algorithms, providing a stronger platform when comparing it with MS Azure ML Services and Google ML Engine.

Incentivized

Compared to Synapse & Snowflake, Databricks provides a much better development experience, and deeper configuration capabilities. It works out-of-the-box but still allows you intricate customisation of the environment. I find Databricks very flexible and resilient at the same time while Synapse and Snowflake feel more limited in terms of configuration and connectivity to external tools.

• Positive: It has allowed us to work with our overseas teams without any large hardware investing.
• Positive: Pre-trained models significantly reduce the time to develop solutions for our clients.
• Negative: Since it's a relatively new tool, you have to be careful about not paying for large errors while learning to use the tool.

Incentivized

• The ability to spin up a BIG Data platform with little infrastructure overhead allows us to focus on business value not admin
• DB has the ability to terminate/time out instances which helps manage cost.
• The ability to quickly access typical hard to build data scenarios easily is a strength.

Incentivized