Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
nikita
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
151.
▲
by
nikita
3y ago
Neon CEO here. Definitely. Of course Neon storage is a distributed system and you need to know how to run it. But a) we can help b) Percona is a trusted partner of us that can support self hosting for you.
152.
▲
by
nikita
3y ago
Neon CEO. We are certainly not going to sunset Neon any time soon. We are extremely well funded and also growing super quickly. Expect some exciting announcements soon!
153.
▲
by
nikita
3y ago
(neon CEO) This is true. Neon however offers bottomless storage and D1 is 100Mb currently going to 1Gb.
154.
▲
by
nikita
3y ago
Well it’s much much harder. Query plans over the distributed system should be different and transaction coordination is different when queries span shards. It’s impossible to give 100% performance compatibility.
155.
▲
by
nikita
3y ago
1. Right now cold start is 3-5 sec. We are actively working on bringing it down. This is our users #1 complaint 2. Yes to pg bouncer. You have two connection strings with and without it 3. Yes. Check out our serverless driver.
156.
▲
by
nikita
3y ago
Agree on the callout. This one we are going to enable soon so it's fixable. So the correction is that it's architecturally possible, but temporarily disabled. Hope we will be able to run Supabase on it soon! Also there are some st
157.
▲
by
nikita
3y ago
Neon CEO here. Much much better :) On a serious note, Neon is Postgres and Planetscale is MySQL. Neon has 100% compat with Postgres and Planetscale supports most but not all MySQL. Neon has unlimited storage a single node compute. Planetsca
158.
▲
by
nikita
3y ago
Please let us know what Neon performance issue you are having. We have been steadily working on performance and it keeps getting better. Our next ongoing investment is cold starts.
159.
▲
by
nikita
4y ago
https://twitter.com/rauchg/status/1644099739959590912?s=46&t...
160.
▲
by
nikita
4y ago
I’m CEO of Neon. Happy to answer any questions
161.
▲
Autoscaling Postgres
(neon.tech)
6 points
by
nikita
4y ago
|
1 comments
162.
▲
by
nikita
4y ago
I’m CEO of Neon. Happy to answer questions.
163.
▲
Deep Dive into Neon storage engine that enables serverless Postgres
(neon.tech)
16 points
by
nikita
4y ago
|
5 comments
164.
▲
by
nikita
4y ago
Take a look at this issue: https://github.com/neondatabase/autoscaling/issues/104 . There is an image there that explains it.
165.
▲
by
nikita
4y ago
Firecracker doesn’t support live migrations. There is a new project called cloud hypervisor and it showed a lot of promise, but we struggled to make it works and reverted to QEMU As for k8s its an ongoing debate internally if the complexity
166.
▲
by
nikita
4y ago
I’m CEO at Neon. Happy to answer questions.
167.
▲
Scaling serverless Postgres: How we implement autoscaling
(neon.tech)
24 points
by
nikita
4y ago
|
9 comments
168.
▲
by
nikita
4y ago
100%
169.
▲
by
nikita
4y ago
You can use in anywhere. We will keep working to drive GLOBAL latency down. As in connect to Neon from anywhere.
170.
▲
by
nikita
4y ago
Serverless environments are a matter of fact. They exist, they are super convenient, and people want to use Postgres in them. This is a bridge for such people. Yes, it requires some sophisticated engineering, but it also enables to have les
171.
▲
by
nikita
4y ago
We are working with the Cloudflare team and see if they can build it. This is a great idea.
172.
▲
by
nikita
4y ago
Potentially. We will follow what our users will ask us to do.
173.
▲
by
nikita
4y ago
How about private link?
174.
▲
by
nikita
4y ago
Small as in 8kb page. A sizable Postgres database would have millions of them. Lots of stuff on the web. Quick googling found: https://www.upsolver.com/blog/small-file-problem-s3
175.
▲
by
nikita
4y ago
> I have a number of workloads I'd migrate to you over the next few weeks if you're ready for it. What is the state of Neon? Please do we will support it! We have 22K hosted databases on the platform and are quite stable. >
176.
▲
by
nikita
4y ago
We are looking at private link for this. Will this work for you?
177.
▲
by
nikita
4y ago
Compaction is performed only by pageserver and only for L0 layers. But L0 layers can be offloaded to S3 and loaded back. So we actually perform compaction of S3 layers (but we download them to the pageserver).
178.
▲
by
nikita
4y ago
Yes. What's your use case? Security or egress costs (those are 0 if you are in the same region).
179.
▲
by
nikita
4y ago
The storage works at the page level. Pageservers provide low latency reads and safekeepers low latency writes. Then we move cold data to S3. Think about safekeepers + S3 being the system of record for most recent + historical data. And page
180.
▲
by
nikita
4y ago
Yes, we are working on this at the moment. Since we control storage we will be implementing this at the storage level. From there we are thinking to expose <project_id>.read.neon.tech and <project_id>.write.neon.tech and for rea
More ›