> what Databricks does It's an ancient African word that means "I am because I can't install Apache Spark".
Just install Apache Spark they said. It will be fun they said. If you have the money, having a managed Spark instance with a bunch of added features can be a big win for some. There is a lot that goes into Spark maintenance.
It also apparently includes some performance optimizations because they control both the hardware and software. And Delta Lake is pretty cool, and hosted MLFlow integration.
Going to beat a dead horse, but 30 days to migrate your database over ? I hope nobody was seriously using it in production, otherwise it's going to be a fun month for them.
The real concern is for those who don't get the memo until day 31
Going to beat a dead horse, but 30 days to migrate your database over ? I hope nobody was seriously using it in production, otherwise it's going to be a fun month for them.
Putting business critical data on a mom and pop service called bit.io was the first mistake.
Reluctantly agreeing with you. So.. you can’t trust a small shop because an MBA corp dev team at some enterprise shop is always lurking around the corner. But if you go to the behemoth instead, you can get equally screwed because you don’t mean anything to their bottom line (see exhibit Google). The commercial software “service” industry is really fucked. I don’t want another tech bust, but we sure as hell deserve one.
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"…
Of all the stupid tech terms in the world, for some reason “data lakehouse” grates horribly in my head every time I hear it.
I hope the marketer who came up with it got the lakehouse they were dreaming of.
Putting business critical data on a mom and pop service called bit.io was the first mistake.
Reluctantly agreeing with you. So.. you can’t trust a small shop because an MBA corp dev team at some enterprise shop is always lurking around the corner. But if you go to the behemoth instead, you can get equally screwed because you don’t mean anything to their bottom line (see exhibit Google). The commercial software “service” industry is really fucked. I don’t want another tech bust, but we sure as hell deserve on…
I feel like we learned 20 years ago that buying proprietary software has a bunch of problems, so we switched to open source software. But in the last 10 years, we started buying software services, and now we have all those problems back again (corporate stability, vendor lock-in, principal agent problems, etc.). Maybe we will learn how to run our own software at some point without fully staffed teams of SREs?
I haven't heard of either of those companies. I don't even fully understand what Databricks does. But it's clear that they have no problem shutting down a production database offering with 30 days notice, and have the gall to title this action "Investing in the Developer Experience". If this doesn't send a message that you shouldn't trust them with anything important, I don't know what would.
> I don't even fully understand what Databricks does
The naming is really confusing. When I brick my console it's broken. I'm not sure I want to brick my data :(
Reluctantly agreeing with you. So.. you can’t trust a small shop because an MBA corp dev team at some enterprise shop is always lurking around the corner. But if you go to the behemoth instead, you can get equally screwed because you don’t mean anything to their bottom line (see exhibit Google). The commercial software “service” industry is really fucked. I don’t want another tech bust, but we sure as hell deserve on…
I feel like we learned 20 years ago that buying proprietary software has a bunch of problems, so we switched to open source software. But in the last 10 years, we started buying software services, and now we have all those problems back again (corporate stability, vendor lock-in, principal agent problems, etc.). Maybe we will learn how to run our own software at some point without fully staffed teams of SREs?
> Maybe we will learn how to run our own software at some point without fully staffed teams of SREs?
Just install Apache Spark they said. It will be fun they said. If you have the money, having a managed Spark instance with a bunch of added features can be a big win for some. There is a lot that goes into Spark maintenance.
It also apparently includes some performance optimizations because they control both the hardware and software. And Delta Lake is pretty cool, and hosted MLFlow integration.
Databricks built a proprietary vectorized accelerator for Spark they call Photon. It's not just that they've tuned OSS Spark especially well.
Till the time they are also bought and "sunsetted." That's the problem with all these shiny startups.
Neon CEO. We are certainly not going to sunset Neon any time soon. We are extremely well funded and also growing super quickly. Expect some exciting announcements soon!
coW? So devs can have their ephemeral databases in seconds at no cost? Only the reads and writes they use and the “delta” storage of their thin clone?
What was the original meaning? When I hear "serverless" I think basically: 1. I don't have to think about or manage any servers 2. Usage is metered at a very fine-grained level (per X requests to the API/per GB of data/etc) 3. No fixed cost. You only pay for usage. Was there a different meaning originally?
Distributed apps. No central server involved. Peer to peer is one. Or each app is a server too and the information propagates in ripple like style. You connect to me, we sync, then another connects to me and this way the info that only you had now he has it too (and me of course). That's the original serverless idea. Not this walled garden crap with "cloud". Cloud is just a computer that is not yours and anything you…
> Distributed apps. No central server involved. Peer to peer is one. Or each app is a server too and the information propagates in ripple like style. You connect to me, we sync, then another connects to me and this way the info that only you had now he has it too (and me of course). That's the original serverless idea.
I don't remember those ever being called "serverless". Certainly "peer to peer" or "distributed" have a lot more traction.