Databricks Reviews & Product Details

What I like best about Databricks is how it simplifies large-scale data processing and collaboration in one platform. The integration with Spark and cloud service makes handling big data much more efficient. I also like the notebook environment, which makes it easier for teams for works together on analytics and machine learning tasks. Review collected by and hosted on G2.com.

One thing I dislike about Databricks is the platform can feel complex for new users, especially when managing clusters and configurations. Pricing can also become expensive with larger workloads if resources are not optimized carefully. While integrations and AI features are powerful, the onboarding process and support documentation could be more beginner-friendly. Review collected by and hosted on G2.com.

in my role i focus on designing scalable and future ready data platform, and databricks has become a key part of that architecture i have used it across multiple project for building data pipelines, enabling analytics, and support data science teams. what stand out it brings engineering, analytics and machine learning into one platform, which simplifies overall data architecture. the biggest strength is the lakehouse approach ., it combines the flexibility of a data lake with the reliability of a data ware house, this helps to avoid maintaining separate system for storage and analytics, i also like how well it handles large scale processing using spark, whether its batch or steaming data, it performs consistently when configured properly. collaboration is another strong point, teams can work together in notebooks, share logic, and reuse code easily, which improves productivity across departments. the UI is designed for well, notebooks are clean and flexible and switching between SQL , python and scala is smooth. it integrates well with AWS , Azure and GCP and Airflow. performance is strong for large scale workloads . the AI features like Genie is very useful. Review collected by and hosted on G2.com.

the biggest concern is cost control, if clusters are not managed properly or left running longer than needed, cost can increases faster than expected, auto scaling is helpful but without monitoring , it can still lead to higher usage. sometimes starting cluster can take time, especially when you just want to run quick tests or small jobs, this can slow down development and reduce productivity during short tasks. when something fails in a pipeline or job, debugging is not always easy, logs can be detailed, but tracing the exact issues in complex workflows can take time. Review collected by and hosted on G2.com.

The UX is one of the strongest parts. The notebook experience is clean and intuitive, collaboration is straightforward, and moving between exploration, experimentation, and production workflows feels seamless. It has enough flexibility for advanced users while still being approachable enough that onboarding new team members is fast. People can usually become productive quickly without spending weeks learning platform-specific quirks.

The integrations are also excellent. It works smoothly with the broader cloud ecosystem and connects well with data sources, orchestration tools, model serving infrastructure, and external systems. That interoperability makes it much easier to move from prototype to deployed pipeline without constantly rebuilding connectors or managing glue code.

Performance has been consistently strong, especially when working with distributed workloads and large-scale feature engineering. Spark optimization, cluster management, and managed infrastructure significantly reduce operational overhead, which lets me focus more on model development and analysis rather than environment tuning. For iterative experimentation, spin-up times and overall responsiveness are noticeably better than many alternative managed platforms. Review collected by and hosted on G2.com.

One area where Databricks could improve is pricing. The platform delivers strong capabilities, but costs can escalate quickly for high-frequency or real-time workloads. For use cases involving continuously running low-latency tick pipelines, streaming market data, or iterative model retraining, the pricing can become fairly steep relative to the infrastructure being consumed. It sometimes feels like there’s a meaningful premium for convenience and managed orchestration, which can make cost optimization a constant consideration.

The AI integration is another area that still feels somewhat uneven. While there’s a clear push toward positioning the platform as an end-to-end AI/ML environment, some of the newer AI-focused features feel more like ecosystem additions than deeply integrated workflow improvements. In practice, there are still cases where custom tooling or external frameworks provide more flexibility and transparency, particularly for specialized model development, experimentation, and real-time inference use cases.

There can also be some complexity around tuning clusters and managing costs efficiently at scale. While the abstractions are helpful, getting the best performance-to-cost ratio sometimes requires deeper platform knowledge than the “fully managed” positioning might imply.

Overall, the platform is very strong technically, but pricing for always-on data-intensive workloads and the maturity of some AI-native capabilities are the two biggest areas where I’d like to see improvement. Review collected by and hosted on G2.com.

Genie code and the inline Assistant were the most helpful tools for me on my project. They helped me debug a 2k-line codebase and clearly explained why I wasn’t getting accurate data. It also provided a query to run in my source system (SQLMI). By running the discrepancy script in parallel on the source and target, I was able to debug the entire code much faster and improve my productivity. Overall, it cut my work time from about 8 hours down to around 1 hour. Review collected by and hosted on G2.com.

In Delta Sharing, there isn’t a catalog-level SELECT permission, and I sometimes think having that would be helpful. Also, when I use the Genie code inside a VM, it can make the website unresponsive at times. These are areas that could be improved. Review collected by and hosted on G2.com.

Databricks has transformed how our team handles end-to-end data workflows. A few standouts:

UI/UX: The notebook interface is intuitive, and the SQL editor feels polished which switching between Python, SQL, and Scala in the same workspace saves constant context-switching.

Integrations: Native connectors to Azure, Unity Catalog, and Delta Sharing mean we spend less time on plumbing. Lakehouse Federation lets us query external sources without moving data, which was an unexpected win.

Performance: Delta Lake's auto-optimization and liquid clustering noticeably reduced our query times. Photon engine on heavy aggregations is a game-changer for near real-time dashboards.

Pricing/ROI: The DBU model takes getting used to, but consolidating our data warehouse, ETL, and ML tooling into one platform cut our overall infrastructure spend significantly.

Support/Onboarding: Databricks Academy and the built-in documentation made onboarding new engineers faster. The community forum is surprisingly active for niche questions.

AI/Intelligence: Genie (AI/BI) lets business users ask questions in plain English and get accurate results reducing ad hoc requests to our data team by a noticeable margin. Databricks Assistant inside notebooks also accelerates code generation and debugging. Review collected by and hosted on G2.com.

While Databricks is powerful, there are real friction points worth mentioning:

UI/UX: The interface can feel overwhelming for new users have the navigation between Workspaces, Catalogs, and SQL Warehouses isn't always intuitive. Folder and notebook organization could be more structured out of the box.

Integrations: Some third-party connectors still require manual configuration and custom code. Lakehouse Federation is promising but occasionally inconsistent with certain source systems, needing extra troubleshooting.

Performance: Cluster startup times remain a pain point cold starts on interactive clusters can disrupt fast-paced workflows. Serverless compute helps but isn't universally available across all features yet.

Pricing/ROI: The DBU-based pricing model lacks transparency for newer teams. It's easy to rack up unexpected costs without careful cluster policies and monitoring in place. A more straightforward cost estimator would help significantly.

Support/Onboarding: Enterprise support response times can be slow for non-critical tickets. For complex architectural issues, getting to the right expert often takes multiple escalations.

AI/Intelligence: Genie works well for standard queries but struggles with complex multi-table logic or domain-specific terminology without significant fine-tuning. The Databricks Assistant inside notebooks occasionally generates outdated or incorrect API suggestions. Review collected by and hosted on G2.com.

I like Databricks for its scalability and all-in-one environment for data engineering, analytics, and machine learning. It allows me to process large datasets efficiently while keeping workflows organized in one platform. The scalability is very valuable because it lets me handle growing data volumes and complex workloads without performance issues. As projects expand, the platform can scale resources efficiently. Review collected by and hosted on G2.com.

Some features can have a learning curve, especially for new users working with advanced configurations or cluster management. The interface could also be more intuitive in certain areas. The setup was relatively smooth for core features, but some advanced settings like cluster optimization, permissions, and integrations required more time and technical knowledge. Review collected by and hosted on G2.com.

What I like most is the performance in processing large volumes of data with Spark, the collaborative notebooks that facilitate teamwork, and the integrations with AWS and BI tools, which make the entire data flow more efficient. Review collected by and hosted on G2.com.

The cost can be high depending on the usage, and some parts of the interface, such as cluster and job configuration, are not very intuitive at first. Additionally, the learning curve can be somewhat steep for new users. Review collected by and hosted on G2.com.

What I like best about Databricks is its powerful and unified analytics ecosystem. Features like Unity Catalog and Metastore make data governance and access control seamless, while the Lakehouse architecture combines the best of data lakes and warehouses. PySpark support, dbutils, and collaborative workspaces make development efficient, and serverless compute simplifies scaling without infrastructure overhead. Review collected by and hosted on G2.com.

What I dislike about Databricks is the slow startup time of all-purpose clusters, which can interrupt workflow and reduce productivity. Additionally, Git integration can feel a bit sluggish at times, especially during commits or syncing, making version control less seamless than expected. Review collected by and hosted on G2.com.

i am working as a Data management specialist and using databricks regularly for handling data pipelines, large scale data processing, and governance tasks, i like most is that databricks provides a single unified platform for data engineering , analytics and AI , instead of using multiple tools. everything is available in one place, the lakehouse architecture is very useful because it combines data warehouse and data lake capabilities, so we can manage both structured and unstructured data efficiently. performance is very strong, especially with apache spark, it can process very large datasets quickly. i also like the collaborative notebooks where teams can work together using SQL, python or scala. Review collected by and hosted on G2.com.

one issue is that it has a steep learning curve, especially for new users who are not familiar with spark or distributed systems. cost management can also be challenging , it clustered are not optimized properly it can become expensive, sometimes too many features and configuration can makes it complex to manage for smaller teams. sometimes the platform feel complex. with many feature and configuration which can be difficult for smaller teams to manages. it it a powerful platform, but complexity and cost control are the main challenges in daily use. Review collected by and hosted on G2.com.

Databricks' ability to seamlessly integrate everything is what I find most appealing. When working on actual projects, it really makes a big difference that you don't have to switch between several tools for data engineering, analysis, and machine learning.

The collaborative element is very noteworthy. Teams may easily collaborate without things becoming messy thanks to the notebooks' fluid and dynamic feel. For significant data work, it resembles Google Docs almost exactly.

I also really like how efficiently it manages large amounts of data without making it seem difficult. Even when working with large datasets, the platform feels user-friendly and can be scaled up when necessary.

Additionally, it makes perfect sense from an AI/ML standpoint. You are able to construct, Review collected by and hosted on G2.com.

Databricks can initially feel a little overwhelming, which is something I don't like. Clusters, notebooks, jobs, workflows—there's a lot going on, and if you're new, it takes some time to truly grasp how everything works together.

Cost control is another drawback. It is undoubtedly strong, but expenses might quickly increase if you are careless with cluster usage or auto-scaling settings. To keep everything under control, you need to exercise some self-control and keep an eye on things.

Databricks can initially feel a little overwhelming, which is something I don't like. Clusters, notebooks, jobs, workflows—there's a lot going on, and if you're new, it takes some time to truly grasp how everything works together.

Cost control is another drawback. It is undoubtedly strong, but expenses might quickly increase if you are careless with cluster usage or auto-scaling settings. To keep everything under control, you need to exercise some self-control and keep an eye on things. Review collected by and hosted on G2.com.