Caffe Deep Learning Framework vs. Databricks Lakehouse Platform

Caffe is only appropriate for some new beginners who don't want to write any lines of code, just want to use existing models for image recognition, or have some taste of the so-called Deep Learning.

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

• Caffe is good for traditional image-based CNN as this was its original purpose.

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

• Caffe's model definition - static configuration files are really painful. Maintaining big configuration files with so many parameters and details of many layers can be a really challenging task.
• Besides imagine and vision (CNN), Caffe also gradually adds some other NN architecture support. It doesn't play well in a recurrent domain, so we have to say variety is a problem.
• Caffe's deployment for production is not easy. The community support and project development all mean it is almost fading out of the market.
• The learning curve is quite steep. Although TensorFlow's is not easy to master either, the reward for Caffe is much less than the TensorFlow can offer.

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.

TensorFlow is kind of low-level API most suited for those developers who like to control the details, while Keras provides some kind of high-level API for those users who want to boost their project or experiment by reusing most of the existing architecture or models and the accumulated best practice. However, Caffe isn't like either of them so the position for the user is kind of embarrassing.

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.

• Since we stopped using Caffe before it can reach the production phase, there is no clear ROI that can be defined.

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