Databricks Reviews

We use this solution to process data, for example, data validation.

The main features of the solution are efficiency.

We were trying to process 300 million records over 10 years. If you are processing that high number of records through the ADF pipeline with, for example, Azure, it took approximately six hours. In order to reduce the burden on our ADF pipeline, we wrote a simple code in this solution where we can read and write to the file into the temporary Storage Explorer. By going through this solution, we were able to complete the processing of the data in half an hour.

The technology that allows us to write scripts within the solution is extremely beneficial. If I was, for example, able to script in SQL, R, Scala, Apache Spark, or Python, I would be able to use my knowledge to make a script in this solution. It is very user-friendly and you can also process the records and validation point of view.

The ability to migrate from one environment to another is useful.

There should be better integration with other platforms.

I have been using this solution for two years.

I have approximately 20 users using this solution in my organization. We have plans to increase our usage in the future.

There is no installation required. It is easy to use, for example, in Azure it is available, you subscribe, and use it.

The solution uses a pay-per-use model with an annual subscription fee or package. Typically this solution is used on a cloud platform, such as Azure or AWS, but more people are choosing Azure because the price is more reasonable.

I rate Databricks a nine out of ten.

We use the solution for business engineering.

The solution is very simple and stable.

The tool should improve its integration with other products.

I have been using the solution for around two years.

I would rate the product’s stability a seven out of ten.

I would rate the tool’s scalability a seven out of ten.

The solution is very easy to setup. I would rate its setup a ten out of ten.

I would rate the tool’s pricing an eight out of ten.

The tool’s performance is great. I would rate it an eight out of ten.

I am using Databricks in my company.

The most valuable feature of Databricks is the notebook, data factory, and ease of use.

I have been using Databricks for approximately nine months.

The performance and stability of Databricks are good. It is quick and I have not had problems.

Databricks is highly scalable.

We have 200 people using the solution in my organization.

When I used the support, I had communication problems because of the language barrier with the agent. The accent was difficult to understand.

I have not worked with another solution prior to Databricks.

The price of Databricks is reasonable compared to other solutions.

I rate Databricks an eight out of ten.

The primary use is for data management and managing workloads of data pipelines.

Databricks can also be used for data visualization, as well as to implement machine learning models. Machine learning development can be done using R, Python, and Spark programming.

Databricks gives you the flexibility of using several programming languages independently or in combination to build models.

The quick visualization of the data is very good.

The workload management functionality works well.

Databricks requires writing code in Python or SQL, so if you're a good programmer then you can use Databricks.

I have been using Databricks since 2017. I am no longer using it personally, although my team is, and will continue to do so in the future.

Databricks is quite popular these days and it appears to be stable. I have not found any issues with stability.

Databricks is scalable, regardless of which cloud provider is being used. It is supported on Microsoft Azure, AWS, and they have their own cloud as well.

For a small workload, Databricks may not be worth the costs. However, for larger workloads, Databricks is a very good solution.

In my previous organization, there were between 10 and 15 users.

The technical support is handled by Microsoft partners and because we had premium support, it was easy to get. That said, I did not require any support.

I have not used tools that are similar to Databricks for workload management, but Azure ADFv2, Google BigQuery, SAS are some the most powerful tools in this space, that I have used in the past. I have also heard of Dataiku and other tools but I have not used them. The only things that I have used are tools written in Python or scripting languages.

There is no installation required.

Databricks uses pay-per-use model, where you can use as much compute as you need. I think that the cost can be reduced, given that there are more users on the platform, although it is not as expensive as some other solutions like SAS.

As we transition to the Azure cloud, I expect that we will be using Databricks for workloads.

This is a product that I recommend for those who want to scale and have a good budget. It is good for automating a data pipeline and managing workloads. My advice for anybody who is starting to use it is to take the proper training.

Overall, based on my uses, I think that this product is pretty good.

I would rate this solution an eight out of ten.

We used Databricks in AWS on top of s3 buckets as data lake. The primary use case was providing consistent, ACID compliant data sets with full history and time series, that could be used for analytics.

Databricks (delta lake) and the underlying files storage (data lake) is in the centre of the organisation's enterprise data hub. Most of our data is structured (csv files), have some semi-structured (json files) but we are beginning to ingest unstructured (pdf files) and use Natural Language Processing (Textract) to obtain insights driven by key words.  

The Databricks notebooks with SQL and Python provide good intuitive development environment. The Delta Lake, the reading of underlying file storage, the delta tables mounted on top of data lake (AWS in our case) are providing full ACID compliance, good connectivity and interoperability.  

The initial setup is fairly straightforward. The stability is good.

The product is quite ambitious. It's trying to become a centralized platform for all data ingestion, transformation, and analytics needs. It may encounter a stiff competition from best of breed solutions powered by open source software. 

Overall it's a good product, however, it might get challenged over time with with individual best-of-breed products. 

For example in the area of Data Science, RStudio seems to be the industry standard at the moment. RStudio IDE is richer, there are a more out of the box functionalities like a push-button publishing, etc. It's more difficult to run R within Databricks. Especially when it comes to synchronizing the R packages, it legs behind. It's not even supporting the latest version of R 1.3. I believe eventually all analytics will converge into data science. The analytics of the future will be data science, because predicting the future will be one of the most prevalent use cases. The stuff we used to do before, slicing and dicing, drilling through, trend analysis, etc. will become redundant operations after the analytics toolsets become powered by AI/ML and fully automated. Unless the organisations acquire these platforms that can cater for machine learning and artificial intelligence, including natural language processing they will have a hard time surviving.

With Databricks I would like to see more integration with and accommodation of  open-source products. This could be controversial, as it could question the whole configuration and the purpose of the product. I'm pretty sure Microsoft is trying to position it in a monopoly market as they did with Windows and MS Office so that they could charge the premium. We are beginning to see the similar product strategy behind Databricks. 

I've been working with Databricks for about two years. 

From what I know and from what I've heard, talking to our data operations team, it is stable and it's quite powerful. 

Obviously running on top of Spark, ensures fast processing and elasticity for coping with big data volumes, up to 2 petabytes. You can spin up the cluster very quickly, and shut it down. It's elastic.

Excellent customer service from Databricks. Very proactive, constantly attuned to customer needs, even connected us with other customers for knowledge exchange. 

I am an IT Consultant and in the past have used different solutions for ETL on top of databases, particularly if we are talking about data warehousing. However, in the last 6 years I have seen large client using a mixture of open source and proprietory technologies, like Informatica stack with data lake in AWS, or Kafka Confluence with MQ Series on top of mainframes and data lake in AWS, Databricks and Azure data lake, etc.

It was pretty easy to set up. At least, that is my understanding. I'm not the data engineer though. I don't actually do installs and configurations. I explore features and build them in my architecture designs.

We implemented Databricks through vendor, and the vendor was pretty good. 

Don't really know.

I can't speak on pricing of the solution. It's not an aspect of the solution I deal with directly.

The options were Talend, EMC Isilon, native AWS services, and others.

In the current capacity as and Architect and the end user of Databricks I would say I do have confidence that Databricks can provide a wealth of functionalities to start with. 

My advice to future adopters of Databricks would be to be careful about the overall architectural roadmap for this application, adopt a flexible, modular, microservices like architecture whose components could be replaced in the future should they deem inadequate to cater for evolving business needs. 

My division works with Big Data and Data Science, and Databricks is one of the tools for Big Data that we work with. We are partners with Microsoft and we began working with this solution for one specific project in the financial industry.

The most valuable feature is the ability to use SQL directly with Databricks. That is the most relevant thing for my current project.

After deployment, it is easy to load files and query data.

I have seen better user interfaces, so that is something that can be improved.

It was quite hard to deploy.

I have been using Databricks for about one year.

We have not found any bugs yet, although it is only the beginning of our work. I do not have enough information to say for sure.

We have about 200 employees but it is only a small group using Databricks. We are at the beginning so scaling is not something we have had to do.

We have not had to contact technical support because we are Microsoft partners and I am calling a colleague of mine who is helping me directly.

I have used Snowflake and one of the differences is that Snowflake is much easier to deploy.

The first deployment is difficult. It is not straightforward and you have to think about a lot of stuff. It is not really like a SaaS deployment and there are a lot of steps that you have to take.

We have our own team, which includes colleagues from Microsoft. Because the current project is a large client, they would like to see this project succeed.

We find Databricks to be very expensive, although this improved when we found out how to shut it down at night.

Our client is a bank and some of the information can be shared outside of the organization, whereas some of the data is confidential and private. Using a purely on-premises solution would have made it more difficult to share information with the outside, which is one of the reasons that they wanted a cloud-based deployment. 

My advice for anybody who is considering this solution is that it is very good for unstructured or semi-structured data. If, however, you have structured data then I would recommend a columnar database like Snowflake or Vertica. These solutions are easier to deploy.

This is a good solution that is working well, but I don't think that it is really a SaaS.

I would rate this solution a seven out of ten.

We are working with Databricks and SMLS in the financial sector for big data and analytics. There are a number of business cases for analysis related to debt there. Several clients are working with it, analyzing data collected over a period of time and planning the next steps in multiple business divisions.

My organization is a professional consulting service. We provide services for the other organizations, which implement and use them in a production environment. We manage, implement, and upgrade those services, but we don't use them.

Databricks helps crunch petabytes of data in a very short period of time for data scientists or business analysts. It helps with fraud analysis, finance, projections, etc. I like it.

This is exactly the purpose of big data and analytics. It provides the mechanism to process and analyze a stream of information. It's best for share analysis and stream analysis.

Costs can quickly add up if you don't plan for it. 

I've been using Databricks for just over a year.

Databricks is stable. It also helps that their support is included as part of the service.

Databricks is scalable. The only issue is how much money you have for it. For example, if you need to run 100 servers, there's an eight-course with 256 gigabytes of RAM. You run out of money easily. It's charged to your credit card or your account, and you'll have to pay for it if you don't plan for that in advance.

Databricks technical support is excellent. They provided their responses on time, and they're useful. However, I don't have extensive experience with them.

I have used different Microsoft solutions before.

The initial setup depends on the readiness of the team working with Databricks. There is no one template saying that it's easy, and it isn't easy. It can be complex to set up if you don't have a really good plan.

You can get in this environment at least for a test. You can do it in the lab, follow it step by step, and that'll take about an hour. The difficulty depends on the business requirements. 

If it's for training purposes, you can do it in about half an hour, and you're good to go. If you need it to support a business, it will be much more rigorous because multiple divisions would be interested in running their own environment, working with their data.

The price is okay. It's competitive. 

If you're thinking of implementing Databricks, I would recommend working with professionals. It'll help you save time. Also, plan the work and work the plan. Otherwise, it'll be a waste of time and money.

On a scale from one to ten, I would give Databricks a nine.

Our primary use case is to decrease costs and prevent any security press on data. I'm an IT manager and we are customers of Databricks. 

I think what I value is more about the technology itself because you don't need to have too much knowledge to be able to use the solution. 

I think we are using a lot of people to manage this solution. I'd like to see the people using this solution sharing their knowledge. 

We've been using this solution for around two years. 

The stability is okay now although a month after the data load there was a limitation for the first time on the project. That sorted itself out. 

It's a scalable solution. 

We have a good connection with technical support. 

I think the point is that because we'll be working collaboratively in the future, internally and externally, we should compare experiences and exchange knowledge. 

I would rate this solution an eight out of 10.