Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Databricks acquires Neon

databricks.com

Post reply on HN
Print view View original

111–120 of 234 posts

Re: Databricks acquires Neon

#111

Post by plumeria »

joshstrange wrote: post #85
anshumankmr wrote: post #84

Earlier quoted context omitted.

Any alternatives that you are aware of ? Most search results show me Supabase.

Supabase is one that I'll consider, Xata [0] is another one that is interesting. Thankfully I just need "postgres", I don't need branching/PII-clearing/etc. That's all nice to have but I don't need it for my app. I really would prefer a managed DB for multiple reasons but I might need to look at just self-hosting. I might have spent less time futzing with my DB if I had done that from the start instead of going Auror…

Branching is one of the most useful features of Neon.

Re: Databricks acquires Neon

#112

Post by swyx »

Robdel12 wrote: post #45

I applied to neon last week and then the news broke about the acquisition. They rejected it this morning — I have never been happier to receive a rejection to an application. This would’ve been three acquisitions straight for me and… I’m okay, they’re awful. I just want stability. Congrats to the neon team! I use and love neon. Really hope this doesn’t change them too much.

what if you had joined at neon's previous valuation (whatever it was) and got a sudden payday (assuming you had juuuust enough vesting)

Re: Databricks acquires Neon

#113

Post by lars_francke »

matt-p wrote: post #106
lars_francke wrote: post #93

Earlier quoted context omitted.

Anyone looking for an open-source Cloudera alternative based on Kubernetes operators. We're building one (~5 years old now): https://stackable.tech/ & https://github.com/stackabletech/ On-premise open-source S3 is a problem though. MinIO is not something we're touching and other than that it looks a bit empty with enterprise ready solutions.

What's wrong with minio out of curiosity? Ceph an option?

This is at least partially subjective.

https://news.ycombinator.com/item?id=32148007

https://news.ycombinator.com/item?id=35299665

Ceph would be a theoretical option, but a) we don't have a lot of experience with it and b) it's relatively complex to operate. We'd really love to add a lighter option to our stack that's under the stewardship of a foundation.

Re: Databricks acquires Neon

#114

Post by aflukasz »

ko_pivot wrote: post #59
jenny91 wrote: post #58

It's my understanding that Neon had some tech to basically "wake up" the DB when a request came out -- so you could "scale down to zero," if you will. I was hoping to explore this for small personal projects: I by far prefer Postgres and would love an isolated database per project. Is there an alternative for that? Scale-to-zero postgres, basically?

AWS Aurora Postgres Serverless v2 has that capability, though it takes multiple seconds.

> AWS Aurora Postgres Serverless v2 has that capability

Was just about to react to someone being wrong on the internet and say that this is not true. Instead, TIL that this is, in fact, the case. Since 2024Q4.

Thanks for invalidating my stale cache.

Re: Databricks acquires Neon

#116

Post by amazingamazing »

refset wrote: post #103
amazingamazing wrote: post #81

Not too familiar with Neon other than the basics - its premise is that you use S3 as bottomless storage for Postgres and it’s otherwise the same as standard Postgres right? And this is all open source? Why are people paying? Can’t you use a cloud provider and have them host this for you?

> you use S3 as bottomless storage for Postgres [...] Why are people paying? It's vastly more complicated to do this efficiently than you might imagine. Postgres' internal architecture is built around a very different set of assumptions (pages, WAL, local disk etc.) than what the S3 API offers.

I get that, but my understanding is that they opened sourced this itself, no?

Re: Databricks acquires Neon

#117

Post by gniting »

anshumankmr wrote: post #104
joshstrange wrote: post #85

Earlier quoted context omitted.

Supabase is one that I'll consider, Xata [0] is another one that is interesting. Thankfully I just need "postgres", I don't need branching/PII-clearing/etc. That's all nice to have but I don't need it for my app. I really would prefer a managed DB for multiple reasons but I might need to look at just self-hosting. I might have spent less time futzing with my DB if I had done that from the start instead of going Auror…

Same here...I too just need Postgres... Will check out Xata, My workload isn't super critical.

Prisma Postgres is also an option to dig into: https://prisma.io/postgres

Re: Databricks acquires Neon

#118

Post by vibhork »

joshstrange wrote: post #51

I’m incredibly disappointed by this news. I really enjoyed Neon but I seriously doubt I’m going to like Databricks’ stewardship if it. And that’s if they even still care about catering to people like me and don’t jack the prices us. I guess it’s time to go back to the well of managed/serverless Postgres options…

Supabase!

Re: Databricks acquires Neon

#120

Post by joshstrange »

plumeria wrote: post #111
joshstrange wrote: post #85

Earlier quoted context omitted.

Supabase is one that I'll consider, Xata [0] is another one that is interesting. Thankfully I just need "postgres", I don't need branching/PII-clearing/etc. That's all nice to have but I don't need it for my app. I really would prefer a managed DB for multiple reasons but I might need to look at just self-hosting. I might have spent less time futzing with my DB if I had done that from the start instead of going Auror…

Branching is one of the most useful features of Neon.

I believe that, it's a cool concept. But I was too nervous to build on top of that feature, I wanted to maintain my ability to leave Neon easily. After Planetscale (and using their version of schema branching) I didn't want to get pinched again when I went to switch (PS vs Neon branching was/is very different).

I think one of the coolest features of neon is being able to quickly spin up new DBs via the API (single tenant DBs) and while that is cool, my client list is small so manually creating the DBs is not a problem (B2B).

Post reply on HN