Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

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

109,706 Aufrufe • vor 3 Monaten •via X (Twitter)

15 Kommentare

Profilbild von PlanetScale
PlanetScalevor 3 Monaten

Read all about it on our blog:

Profilbild von Pranav Bobde
Pranav Bobdevor 3 Monaten

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 🫡

Profilbild von HSVSphere
HSVSpherevor 3 Monaten

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

Profilbild von Mubashir
Mubashirvor 3 Monaten

such a nice explanation

Profilbild von Vincent Pizzo
Vincent Pizzovor 3 Monaten

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

Profilbild von rikkarth
rikkarthvor 3 Monaten

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

Profilbild von Santi
Santivor 3 Monaten

Another PlanetScale banger

Profilbild von Jos Graas 🇱🇺
Jos Graas 🇱🇺vor 3 Monaten

@chrismunns Nice video!

Profilbild von Indy Singh
Indy Singhvor 3 Monaten

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?

Profilbild von Ξ Calderón 🛡️
Ξ Calderón 🛡️vor 3 Monaten

know I understand!

Profilbild von AJ
AJvor 3 Monaten

@grok how many Postgres instances and servers does ChatGPT run

Profilbild von WenHao
WenHaovor 3 Monaten

amazing

Profilbild von xp Ehsaan
xp Ehsaanvor 3 Monaten

@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 ?

Profilbild von Sebastian Buzdugan
Sebastian Buzduganvor 3 Monaten

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

Profilbild von Chibueze the chef👨‍💻👨‍🍳
Chibueze the chef👨‍💻👨‍🍳vor 3 Monaten

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?

Ähnliche Videos