Azure Databricks is a service available on Microsoft's Azure platform and suite of products. It provides the latest versions of Apache Spark so users can integrate with open source libraries, or spin up clusters and build in a fully managed Apache Spark environment with the global scale and availability of Azure. Clusters are set up, configured, and fine-tuned to ensure reliability and performance without the need for monitoring. The solution includes autoscaling and auto-termination to improve…
N/A
Dataiku
Score 8.5 out of 10
N/A
The Dataiku platform unifies data work from analytics to Generative AI. It supports enterprise analytics with visual, cloud-based tooling for data preparation, visualization, and workflow automation.
N/A
Pricing
Azure Databricks
Dataiku
Editions & Modules
No answers on this topic
Discover
Contact sales team
Business
Contact sales team
Enterprise
Contact sales team
Offerings
Pricing Offerings
Azure Databricks
Dataiku
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Azure Databricks
Dataiku
Considered Both Products
Azure Databricks
Verified User
Anonymous
Chose Azure Databricks
When compared with Snowflake, Azure Databricks have an edge over the integration with ML Flow. ETL in Azure Databricks allows high processing of data compared to Snowflake. Data sharing is better with Snowflake. When compared with Datasphere, integration of Databricks with …
I have found Azure Databricks to be much better than Snowflake for handling bigger, diverse data types. Snowflake is much simpler and better for smaller warehousing. The real time processing is much better in Azure Databricks and we have much more language options. Snowflake is …
Against all the tools I have used, Azure Databricks is by far the most superior of them all! Why, you ask? The UI is modern, the features are never ending and they keep adding new features. And to quote Apple, "It just works!" Far ahead of the competition, the delta lakehouse …
Dataiku was selected for me, but I am happy about that. I like Dataiku for the user experience, it feels less code-y and I like to demo things to non technical stakeholders because they can still follow along. When you open some other notebooks, you can see that peoples eyes …
Strictly for Data Science operations, Anaconda can be considered as a subset of Dataiku DSS. While Anaconda supports Python and R programming languages, Dataiku also provides this facility, but also provides GUI to creates models with just a click of a button. This provides the …
Open source availability is a critical factor given licensing cost of other platforms and budget reasons. Secondly, the available features in the community version covers most of the use cases, thus making it comparable or even outdo commercial versions of other software. …
Anaconda is mainly used by professional data scientists who have profound knowledge of Python coding, mainly used for building some new algorithm block or some optimization, then the module will be integrated into the Dataiku pipeline/workflow. While Dataiku can be used by …
Suppose you have multiple data sources and you want to bring the data into one place, transform it and make it into a data model. Azure Databricks is a perfectly suited solution for this. Leverage spark JDBC or any external cloud based tool (ADG, AWS Glue) to bring the data into a cloud storage. From there, Azure Databricks can handle everything. The data can be ingested by Azure Databricks into a 3 Layer architecture based on the delta lake tables. The first layer, raw layer, has the raw as is data from source. The enrich layer, acts as the cleaning and filtering layer to clean the data at an individual table level. The gold layer, is the final layer responsible for a data model. This acts as the serving layer for BI For BI needs, if you need simple dashboards, you can leverage Azure Databricks BI to create them with a simple click! For complex dashboards, just like any sql db, you can hook it with a simple JDBC string to any external BI tool.
Dataiku DSS is very well suited to handle large datasets and projects which requires a huge team to deliver results. This allows users to collaborate with each other while working on individual tasks. The workflow is easily streamlined and every action is backed up, allowing users to revert to specific tasks whenever required. While Dataiku DSS works seamlessly with all types of projects dealing with structured datasets, I haven't come across projects using Dataiku dealing with images/audio signals. But a workaround would be to store the images as vectors and perform the necessary tasks.
Great for what we use day to day and does what we need it to do. Cost management is not fully developed across the UX and gets expensive very quickly for developing projects. Integrated very well with our Microsoft stack and can be worked on collaboratively which works well for us.
The user experience is very good. Everything feels intuitive and "flows" (sorry excuse the pun) so nicely, and the customization level is also appropriate to the tool. Even as a newer data scientist, it felt easy to use and the explanations/tutorials were very good. The documentation is also at a good level
The amazing part of Dataiku DSS is their customer service. Based on urgency and technical level, you get a reply from the Dataiku engineer when you raise a query. So far, my queries have been pretty complex to solve, so I have received solutions even from the CTO of the company as well, which is why I would describe their customer support as very good.
I have found Azure Databricks to be much better than Snowflake for handling bigger, diverse data types. Snowflake is much simpler and better for smaller warehousing. The real time processing is much better in Azure Databricks and we have much more language options. Snowflake is more expensive but simpler to use. Both are great for different needs.
Dataiku was selected for me, but I am happy about that. I like Dataiku for the user experience, it feels less code-y and I like to demo things to non technical stakeholders because they can still follow along. When you open some other notebooks, you can see that peoples eyes start to glaze over