Databricks Data Intelligence Platform

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

Databricks helps solve the challenge of processing and analyzing large amounts of data efficiently in one platform. It combines data engineering, analytics and AI workflows, which reduce the need for the multiple separate tools. This improves collaboration, speeds up data processing, and helps generate insights much faster.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

it mainly solves the problem of handling large scale data processing and unifying different data workloads in one platform, earlier building and maintaining ETL pipelines require multiple tools and a lot of manual effort, with databricks i can build, run and manage pipelines in one place using spark, which simplifies the overall process, processing big datasets used to require heavy infrastructure setup, databricks handles this using distributed computing, so i can process large amount of data efficiently without worrying about scaling manually.in traditional setup, we needed separate tools for data engineering , analytics , machine learning, it brings all this into one platform, with shared notebooks and a unified workspace, team can collaborate more easily share code, and work on the same data.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

Databricks solves one of the biggest challenges in modern data work: bringing together data access, large-scale processing, and collaborative development in a single environment.

For my work, the biggest benefit is real-time collaboration. It allows multiple people to work against the same datasets, notebooks, and pipelines without the usual friction of fragmented tooling or environment inconsistencies. That significantly speeds up experimentation, iteration, and knowledge sharing across projects, especially when moving quickly on model development or analyzing fast-changing data.

It also solves the challenge of scalable data access and processing. Working with high-volume time-series and transactional datasets requires infrastructure that can process large amounts of data efficiently without constant operational overhead. Databricks abstracts much of that complexity, making it possible to focus on analysis, feature engineering, and model development rather than spending time managing infrastructure.

The practical benefit is faster iteration cycles. I can move from raw data exploration to model experimentation and deployment much more quickly, which is especially valuable when working on real-time analytics, forecasting pipelines, and production-facing ML systems where speed of iteration directly impacts outcomes.

Overall, it reduces engineering friction and makes large-scale collaborative data work significantly more efficient, which translates into faster development, better experimentation, and more reliable deployment of data products.

What do you like best about the product?

It’s straightforward to write and run SQL, schedule workflows, and I especially like the notebook feature. Genie AI is helpful for diagnosing bugs, and it can also answer ad hoc questions whenever I need it.

What do you dislike about the product?

Genie’s AI feature could still use some improvement. It sometimes takes a long time to respond, and with more complex problems it doesn’t always handle them well.

What problems is the product solving and how is that benefiting you?

The workflow is very easy to schedule. It’s also simple to set up alerts, and the visualization makes it easy for me to modify and debug.

What do you like best about the product?

This platform solves developers’ problems by offering features like Genie, Lakeflow Connect, and DLT.

What do you dislike about the product?

Before using it, I want to understand the compute and charges, and how to use it properly. Basically, I need to learn a lot first.

What problems is the product solving and how is that benefiting you?

It solved our data pipeline and dashboard creation challenges. With SDP and AI/BI Genie, we moved from manually managing the data pipeline to simply declaring it in SQL and having everything handled for us. Instead of spending so much time building dashboards, we can now just ask questions in natural language and get the answers we need without wasting a lot of time.