6 ms·
Looks like the acquihire of Bit.io in 2023 wasn't enough to be able to deliver their own OLTP offering https://blog.bit.io/whats-next-for-bit-io-joining-databr
by thiagoeh 1y ago
Looks like the acquihire of Bit.io in 2023 wasn't enough to be able to deliver their own OLTP offering
https://blog.bit.io/whats-next-for-bit-io-joining-databricks-ace9a40bce0d https://blog.bit.io/whats-next-for-bit-io-joining-databricks...
https://www.databricks.com/blog/welcoming-bit-io-databricks-investing-developer-experience https://www.databricks.com/blog/welcoming-bit-io-databricks-...
Or it's just a business decision to corner the market, as someone else said
- mcmcmc 1y ago> Or it's just a business decision to corner the market, as someone else said Given how lax antitrust enforcement is, probably this
- klabb3 1y agoThey aren’t exactly hiding it. I kept my eye on bit.io because they looked very promising. Next day, gone. Shut down immediately. Something is fucky with the investment pipeline because it’s not ”worth” that much on its own, it’s a market dominance play, bad for innovation..
- timenova 1y agoOkay now I am concerned. We're using Neon. We can move easily at this point, but I'm sure they have huge customers storing many terabytes of data where this may be genuinely hard to do. I went to Archive.org and figured out that in 2023, they announced they were shutting down on May 30th, all databases shutdown on June 30th, only available for downloads after that, and deleted on July 30th.
- joshstrange 1y agoSame boat here. Not really looking to have to move but I'm incredibly thankful that I never integrated with Neon more than using Postgres. I don't depend on/need their API or other branching features. I hate that this is what I've become, I want to try some of the cool features "postgres++" providers offer but I actively avoid most features fearing the potential future migration. I got burned using the Data API on Aurora Serverless and then leaving them and having to rewrite a bunch of code.