Azure Databricks vs. Kensho

Centralised notebooks are out directly into production. This can lead to poorly engineered code. It is very good for fast queries and our data team are always able to provide what we ask for. It is a big cost to our business so it is important it runs efficiently and returns on our investment.

Incentivized

• Data Processing and Transformations based on Spark
• Delta Lakehouse when clubbed with an external cloud storage
• Governance using Unity Catalog to unify IAM
• Delta Live Tables is a product, which although relatively newer, has a great potential with the visuals of a pipeline.

Incentivized

• Intuitive interface
• Ease of use
• Providing FAQ or QRGs

Incentivized

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.

Incentivized

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 platform also fares better than it counterparts of Iceberg implementation or a loosely bound Delta Lake implementation of Synapse

Incentivized

• Helped reduce time for collecting data
• Reduced cost in maintaining multiple data sources
• Access for multiple users and management of users/data in a single platform

Incentivized