Databricks Data Intelligence Platform vs. Hugging Face

Medium to Large data throughput shops will benefit the most from Databricks Spark processing. Smaller use cases may find the barrier to entry a bit too high for casual use cases. Some of the overhead to kicking off a Spark compute job can actually lead to your workloads taking longer, but past a certain point the performance returns cannot be beat.

Incentivized

If an organisation has more access to data and have access to high end computers like GPUs it’s recommended to use Hugging face as it will give better accuracy than any other models. If an organisation having less data and has less access to GPUsis looking for decent performance then traditional algorithms are more appropriate than hugging face

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

• Model APIs
• Hugging Face Spaces for deploying demo apps
• Latest updated models available easily
• Vast support for language parsing and other relevant tasks

Incentivized

• Sometimes, when multiple jobs depend on each other in different environments, it is not always easy to see the full workflow in one place.
• It is sometimes difficult to determine which job or cluster contributes more to the overall cost.
• For beginners, cluster configuration may be a little difficult. So more recommendation in the platform can help.

Incentivized

• Most of the Hugging face models are of big size, hence difficult to work if there is no access to high computational system like GPU.
• It’s good to have some visualization tool in hugging face for viewing model architecture.
• I recommend to implement hugging face lite version so that it can run on any system with less specifications.

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.

The most important differentiating factor for Databricks Lakehouse Platform from these other platforms is support for ACID transactions and the time travel feature. Also, native integration with managed MLflow is a plus. EMR, Cloudera, and Hortonworks are not as optimized when it comes to Spark Job Execution. Other platforms need to be self-managed, which is another huge hassle.

Incentivized

There are some other services offer similar capacity as to Hugging Face, but not entirely the same. For example, amazon web services have a machine learning service called Comprehend, which offer a set of easy to use APIs to do machine translation and entity recognition and some other common NLP use case.

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

• Hugging Face is cost and time saving.
• Pay is less, you pay what you use, doesn't affect much.
• Overall positive impact on business.

Incentivized