What does HackerNews think of neon?

Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, branching, and bottomless storage.

Language: Rust

#14 in Database
#13 in PostgreSQL
#17 in PostgreSQL
#55 in Rust
#5 in Serverless
I never heard of either of these, but Neon does look pretty cool. I might try it for some homelab type stuff that doesn't need a database running 24/7.

https://github.com/neondatabase/neon

Will be very interesting to see how it plays out. I'm yet to see the database technology completely licensed as BSL to be successful in Open Source strategy.

Elastic made change after it was very popular, MariaDB is same story, and even more so only uses BSL for "Enterprise" components which have very little community adoption.

We see however other folks, such as Neon picking permissive license for their technology https://github.com/neondatabase/neon

I think for Open Source Project just starting up concern of "Clouds will steal my lunch" is just stupid. If you're worth for clouds to Adopt you're in 0.1% of all Open Source Projects and already "winning" You can WHEN revisit your license, think how to get to that point, rather than create adoption barriers early on

Right now, it should be possible to use anything that is compatible with the S3 API, as our current focus is on getting the product to the market. Once the business model is proven, we'll likely branch out to other clouds, with their storage providers.

If you can't wait that long to run Neon on your own cloud, feel free to contribute an integration to your persistent blob storage: the code is available under APLv2 here: https://github.com/neondatabase/neon/

For now we've focused on making the product production-ready on AWS, so that we can get users to try it out. Once the model has been proven we'll likely branch out to other clouds.

However, if you really can't wait to run Neon on Azure, you could contribute the integration yourself: the code is available under Apache 2 at https://github.com/neondatabase/neon/

We wrote a custom storage layer for postgres, so in our setup, postgres node (k8s pod actually) doesn't store any data, and it is easy to start/stop/reschedule it. So while we actually are DBaaS, the closest analogy here is Aurora or Alloy, not RDS-like setups.

A bit more details are on https://github.com/neondatabase/neon

Thank you! We are super hard at work. You can see our velocity here: https://github.com/neondatabase/neon
> Another approach could be using PostgreSQL as a stateless scalable query execution engine, while stubbing out the storage layer with a remote replicated consistent storage solution.

Also neon:

https://github.com/neondatabase/neon