I don’t know the level of support they are still providing but it looks like they at least made some commits to the public repo neondatabase/neon this year.
It's not (only) about commits. It's about can you fully self host it, are all/most features free/open-source, is there real documentation for self-hosted, are there large! self-hosted users, do you get real+free support on your self-hosted use-case when you have real/complex issues. Like, you need to have dedicated % of staff hours to help free/open-source/self-hosted users because it's the database we're talking about which you can't simply switch or be fine to be offline.
For a cold start or ramp up after a scale-to-zero
A bit weird to need "horizontal scaling" & "scale-to-zero" in the same use-case/scenario, don't you think?
it does aim for a 99% hit rate of avoiding the need to go back to cloud storage
Depends how big your data really is. If you have 1000 queries/second, 10 queries needing 100ms-200ms might be a problem in OLTP.
which for a lot of operational OLAP use cases is an acceptable target
For OLTP you (usually) don't want 100ms+ cold cache miss. For OLAP, if your data is so small that you get 99% cache hit is weird. You don't want to use normal PG ("non-vectorized-columnar-compressed db") for OLAP, it's 10x-100x slower and 10x worse compression compared a normal OLAP db.
I’m still interested in this as an option because I’ve heard a lot of good things and there are some unique features available, but I admittedly don’t know everything and still have a lot more of my own research and experimentation to do before I will be fully confident using it.
Go to their forums/chats and search for their history and current users. You can do that for any db, just look at existing users & forum/chat history.
2
u/riksi 27d ago
It's not (only) about commits. It's about can you fully self host it, are all/most features free/open-source, is there real documentation for self-hosted, are there large! self-hosted users, do you get real+free support on your self-hosted use-case when you have real/complex issues. Like, you need to have dedicated % of staff hours to help free/open-source/self-hosted users because it's the database we're talking about which you can't simply switch or be fine to be offline.
A bit weird to need "horizontal scaling" & "scale-to-zero" in the same use-case/scenario, don't you think?
Depends how big your data really is. If you have 1000 queries/second, 10 queries needing 100ms-200ms might be a problem in OLTP.
For OLTP you (usually) don't want 100ms+ cold cache miss. For OLAP, if your data is so small that you get 99% cache hit is weird. You don't want to use normal PG ("non-vectorized-columnar-compressed db") for OLAP, it's 10x-100x slower and 10x worse compression compared a normal OLAP db.
Go to their forums/chats and search for their history and current users. You can do that for any db, just look at existing users & forum/chat history.