nikita

15 ms·

181.
by nikita 4y ago
I'm CEO of Neon. Happy to answer any questions you might have.
182.
Quicker serverless Postgres connections(neon.tech)
164 points by nikita 4y ago|98 comments
183.
by nikita 4y ago
Neon CEO here. Happy to answer any questions you might have.
184.
by nikita 4y ago
Subscriptions should still work with scale to 0. NOTIFY/LISTEN doesn't: https://neon.tech/docs/reference/compatibility . We will have an option to not scale all the way to 0 to support this scenario.
185.
by nikita 4y ago
yes to triggers - it's full postgres. logical replication is not exposed just yet, but soon
186.
by nikita 4y ago
Yes, we are partnering with many companies like Hasura and Replit to help with managed Postgres. Since Neon scales to 0 and also autoscales to your workload it very economical for the long tail of low usage customers.
187.
by nikita 4y ago
(Neon CEO) We are launching our paid tier March 15th and will be production ready shortly after. We are running 20K+ databases and measuring reliability and uptime. Generally reliability is a function of architecture (we are solid there), g
188.
by nikita 4y ago
Yes it does! As of Feb 14th: Valentines day present. https://neon.tech/docs/release-notes
189.
by nikita 4y ago
One database per user is something many of our customers are already using today. I think if there are millions of users it’s a bit of an overkill. Because likely you will have some very light users that you can still collocate on one datab
190.
by nikita 4y ago
Launching on mar 15th
191.
by nikita 4y ago
Disclosure. I'm CEO of Neon (neon.tech). One of the premises that we have is the ability to instantly create a test environment by creating a branch. I'd love to hear what you think about it.
192.
by nikita 4y ago
Neon CEO here. We are working on becoming first party service on several major problems now. We will be happy to provide this for Fly. Kurt and I have been chatting. Fly wants cross region replication which is coming soon. Once it's th
193.
by nikita 4y ago
So the market looks like this: - Tier1: Unique large scale workload: think about moving money around. This is ~$10-20Bln market mostly dominated by Oracle, Microsoft and IBM. All next gen scale systems kind of forced to play in this market.
194.
by nikita 4y ago
Stay tuned. It's coming very very soon.
195.
by nikita 4y ago
We used mmap extensively and it took a gigantic effort to purge it out of the codebase in SingleStore. Lots of issues the biggest one is that munmap has a mutex and you incur a lot of contention. The second one is that mmap prevents you fro
196.
by nikita 4y ago
I think lots and lots of benchmarks are useful internally. They highlight where the soft spots are. This is however very different from publishing benchmark results. As a dbaas vendor we should publish benchmarks that your user base really
197.
by nikita 4y ago
The reason we run OLAP bench is because when you separate storage full table get impacted: you fetch pages from remote storage one by one and the mitigation is prefetch. So our goal is to be on par with vanilla Postgres. We don't care
198.
by nikita 4y ago
Neon is hiring systems (Rust, C) engineers, postgres hackers (C), and backend engineers (Go)
199.
by nikita 4y ago
> The resource mismatch currently leaves a lot of compute sitting idle in practice. When separate storage is multi tenant and compute is elastic you can really squeeze more efficiency. With that you can keep utilization extremely high, b
200.
by nikita 4y ago
Adam, you still synchronously replicate each log record to 2 places, right? Technically this should be roughly equivalent to writing into a consensus. And use write through cache for reads.
201.
by nikita 4y ago
I wouldn't say HTAP is an across the board trend. The need is mostly in the enterprise where we see high value mixed workloads. Neon will take a Postgres centric POV. I consider a few approaches, but not committing to any particular at
202.
by nikita 4y ago
Neon CEO here. There are a number of ideas in the database space that the industry is adopting across the board: - Separation of storage and compute (Neon, AlloyDB, Aurora). Every cloud database should built one. It's a big undertaking
203.
by nikita 4y ago
We will certainly make it possible. There is something to also consider: software development lifecycle and native support for previews, schema PRs, and deploys. Lots to build to give lots of confidence to a developer that a PR won't b
204.
by nikita 4y ago
You are right. We will make it work soon
205.
by nikita 4y ago
To elaborate Neon is designed deliberately to plug into the Postgres ecosystem. So all of the ecosystem works out of the box. Supabase seems to be vertically integrated. But Paul should comment on that
206.
by nikita 4y ago
I think we innovate on different parts of the stack. Neon is offering separation of storage and compute and serverless. Theoretically you can run Supabase on top of Neon
207.
by nikita 4y ago
Yes. Also it was an easier thing to do and ship quickly. We are going to get very tight on latencies and if that would require building it into Postgres we will do so
208.
by nikita 4y ago
100GB
209.
by nikita 4y ago
We have some ideas of compiling Postgres to wasm and sync with the mothership in the cloud. But we haven’t funded the work. Check out electricsql they are looking at this problem.
210.
by nikita 4y ago
Storage is multi tenant and bottomless. Unused storage spills to S3 and is cheaper. We pass savings to our users

More ›