We use Dremio for data engineering.
The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.
Use our online form to submit your review. It's quick and you can post anonymously.
We use Dremio for data engineering.
Dremio has resolved my data lineage and data governance problems. The solution has also resolved the data availability for a different range of users, which used to be a problem.
Dremio allows querying the files I have on my block storage or object storage. The solution gives me a place where I can play around with the data virtually by creating VDSs or PDSs. Dremio works just like a data warehouse on top of my data lake, which is interesting.
Dremio's interface is good, but it has a few limitations. I cannot do a lot of things with ANSI SQL or basic SQL. I cannot use the recursive common table expression (CTE) in Dremio because the support page says it's currently unsupported.
The use case I am working on requires building trees and hierarchical structures. Most of the time, it requires complex nested data structures to be made simpler for end users. It would be good if Dremio could provide a way to create trees just like Oracle does using commands like CONNECT BY and NO CYCLE.
You can use a few languages to simplify complicated JSON and XML. It would be very helpful if Dremio could provide a solution to simplify building trees and building meaningful data from complex data.
I rate Dremio ten out of ten for stability.
I rate Dremio ten out of ten for scalability.
I rate Dremio ten out of ten for the ease of its initial setup.
We implemented the solution through an in-house team. Dremio's deployment can be done quickly.
Overall, I rate Dremio ten out of ten.
We have been using it to build one of our frameworks. We primarily use Dremio to create a data framework and a data queue. It's being used in combination with DBT and Databricks.
We're still in the exploration phase with Dremio, so it's a bit early to determine its most valuable feature. We're currently deploying it across different departments for various use cases and learning from these internal applications.
We've faced a challenge with integrating Dremio and Databricks, specifically regarding authentication. It is not shaking hands very easily. We had to set up two different VMs and execute them in a different manner and integrate them.
I've been using Dremio for about two to three months now. However, one of our teams has been using it for the past year.
From my three months of experience, I haven't noticed any stability issues with Dremio.
In my department, which focuses on data and AI, we have about 538 people. I'm not sure how many are actively using Dremio.
The installation process was quite smooth and didn't present any issues.
We currently have Dremio on the cloud. For proof of concept (POC) purposes, we are using it on-premises.
We are currently evaluating Dremio against other similar products. But at first glance, I would recommend using Dremio.
Considering my limited access and experience over these three months, I would rate Dremio around a seven out of ten.
