Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

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

109,706 görüntüleme • 1 ay önce •via X (Twitter)

15 Yorum

PlanetScale profil fotoğrafı
PlanetScale1 ay önce

Read all about it on our blog:

Pranav Bobde profil fotoğrafı
Pranav Bobde1 ay önce

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 profil fotoğrafı
HSVSphere1 ay önce

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 profil fotoğrafı
Mubashir1 ay önce

such a nice explanation

Vincent Pizzo profil fotoğrafı
Vincent Pizzo1 ay önce

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

rikkarth profil fotoğrafı
rikkarth1 ay önce

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

Santi profil fotoğrafı
Santi1 ay önce

Another PlanetScale banger

Jos Graas 🇱🇺 profil fotoğrafı
Jos Graas 🇱🇺1 ay önce

@chrismunns Nice video!

Indy Singh profil fotoğrafı
Indy Singh1 ay önce

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 🛡️ profil fotoğrafı
Ξ Calderón 🛡️1 ay önce

know I understand!

AJ profil fotoğrafı
AJ1 ay önce

@grok how many Postgres instances and servers does ChatGPT run

WenHao profil fotoğrafı
WenHao1 ay önce

amazing

xp Ehsaan profil fotoğrafı
xp Ehsaan1 ay önce

@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 profil fotoğrafı
Sebastian Buzdugan1 ay önce

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

Chibueze the chef👨‍💻👨‍🍳 profil fotoğrafı
Chibueze the chef👨‍💻👨‍🍳1 ay önce

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?

Benzer Videolar