正在加载视频...

视频加载失败

768 Postgres servers. A petabyte of data. One connection string.

109,706 次观看 • 1 个月前 •via X (Twitter)

15 条评论

PlanetScale 的头像
PlanetScale1 个月前

Read all about it on our blog:

Pranav Bobde 的头像
Pranav Bobde1 个月前

That was beautiful. Even tho i haven't used planetscale yet unfortunately. They are the only DB platform w/ peak deep dives on such core DB topics and i love that. Pls keep pushing such content and the bar 🫡

HSVSphere 的头像
HSVSphere1 个月前

Is the reason why no DB company does anycast because stateful long lasting protocols might start getting routed to the wrong proxy, closing the connection? And specifying the region via dns and thus different IP circumvents this. Truly something is deeply wrong with our tech

Mubashir 的头像
Mubashir1 个月前

such a nice explanation

Vincent Pizzo 的头像
Vincent Pizzo1 个月前

On , any idea when the source will be made available? I’d love to see a comparison with Citus / PgDog too!

rikkarth 的头像
rikkarth1 个月前

claude please produce transcript from the audio of this video and help build the solution in other words, what a great video

Santi 的头像
Santi1 个月前

Another PlanetScale banger

Jos Graas 🇱🇺 的头像
Jos Graas 🇱🇺1 个月前

@chrismunns Nice video!

Indy Singh 的头像
Indy Singh1 个月前

So what's the overhead of the router here? If you have that kind of setup your TPS/QPS must be pretty high, to where the introduction of a router is going to add a some overhead and at that scale it is going to show up right?

Ξ Calderón 🛡️ 的头像
Ξ Calderón 🛡️1 个月前

know I understand!

AJ 的头像
AJ1 个月前

@grok how many Postgres instances and servers does ChatGPT run

WenHao 的头像
WenHao1 个月前

amazing

xp Ehsaan 的头像
xp Ehsaan1 个月前

@grok does this solution save on cost ? Instead of increasing primary server spec vertically, you scale horizontally he shardng when the demand increases for write operation ?

Sebastian Buzdugan 的头像
Sebastian Buzdugan1 个月前

watched one connection string hide shard pain, failover is still the hard part

Chibueze the chef👨‍💻👨‍🍳 的头像
Chibueze the chef👨‍💻👨‍🍳1 个月前

What happened when the shard that is meant to handle a particular data fails ? Does the routing decision grow as the number of shard grows? Also would there be any form of latency or those are negligible?

相关视频