Databricks Lakehouse Platform vs. Paxata

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

Paxata can be highly useful to someone who doesn't like/have any experience with writing codes to treat data before using it as input into BI dashboards. Paxata can accelerate data cleaning in environments where a large amount of unclean data is generated and business decisions on the go are required. It performs really well while dealing with natural language.

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

• Visualize distributions in large data sets effectively which enable the user to quickly spot outliers and treat them appropriately
• Provides recommendation to merge datasets based on matching column values
• The cluster and edit feature in my opinion is its most powerful feature and reduces cardinality in column with text

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

• Doesn't provide recommendation on how to impute values
• There is a lag quite often
• We can say whether a column has errors or quality issues in the first look

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.

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.

Paxata is a much better tool when it comes to handling natural language but Talend provides recommendations on how to impute missing values and outliers. Paxata provides recommendations on dataset tie-ups and joins but Talend doesn't provide any such recommendations. In paxata you can visualize distribution of data in a column and filter them by dragging and selecting the section you'd like to retain

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

• It saves time to clean data
• It reduces the requirement of too many data engineer/stewards and hence adds positive impact on the return of the business

Incentivized