4 ms·
This is interesting... possibly a move by Databricks to try and build on their "data lakehouse" concept to counter the recent "Fabric platform" announcements at
by gdubya 3y ago
This is interesting... possibly a move by Databricks to try and build on their "data lakehouse" concept to counter the recent "Fabric platform" announcements at MS Build.
Databricks coined the "Delta lake" concept and are still (just about) leading the way, but Fabric has the potential from MS to take away that marketshare. Databricks need to improve their "serverless SQL" offering, and add a serious "data warehouse" component alongside the lake.
- itsrobforreal 3y agoI'm perusing the Fabric docs and they are using Delta Lake, Spark and Azure Databricks as part of that solution
- gdubya 3y agoFabric does not use Databricks, but both Databricks and Fabric rely heavily on Delta. Let's just hope that they remain compatible.
- itsrobforreal 3y agoAh, so we're in the "extend" portion of the process
- Scubabear68 3y agoOf all the stupid tech terms in the world, for some reason “data lakehouse” grates horribly in my head every time I hear it.
- fshbbdssbbgdd 3y agoI hope the marketer who came up with it got the lakehouse they were dreaming of.
- vforgione 3y agoFabric may eat some of the descriptive analytics portion of Databricks’ lunch, but for core data engineering workflows there is nothing in the Fabric—or Synapse or Power BI—ecosystem that comes close. There are other fatal flaws to the Spark implementation in Synapse that I think carried over to Fabric. Worst one is the clunkiness/inability to run multiple notebooks concurrently on a cluster.