Shard
3
MENTIONS
3
EPISODES
3
PODCASTS
Search complete. 3 mentions across 3 episodes found for "Shard".
Oct 26, 2026
Supabase’s Plan for a Billion AI-Built Apps
P
5:59Paul CopplestoneGUEST
That's one year.
P
6:00Paul CopplestoneGUEST
So we haven't released Sharding yet.
P
6:02Paul CopplestoneGUEST
I've seen the early prototypes and the designs for how we're doing it, and some of it should land by probably early next year, depending on some of the things that are happening on our platform.
P
6:14Paul CopplestoneGUEST
We've got a lot going on, but we're very confident, and we're happy with the progress.
10 Million QPS . . . Efficiently | Scaling Postgres 440
C
2:38Creston JamisonHOST
So does the disk subsystem have anything to do with it? I don't know.
C
2:42Creston JamisonHOST
So for this test, it looks like they have three worker nodes, which is basically where the data is stored, sharded.
C
2:49Creston JamisonHOST
And their query routers, they used six.
C
2:52Creston JamisonHOST
And with that, they were able to achieve 1.4 million transaction per second.
P
Unknown podcast
MongoDB in Action: Covers MongoDB version 3.0
Oct 24 · 1 Mention
S
22:31speaker_4HOST
But what happens when our startup goes viral and the total volume of data grows so massive that it physically cannot fit onto a single server's hard drive, no matter how much we upgrade it?
S
22:43speaker_6HOST
That is where you move from replication to sharding.
S
22:45speaker_6HOST
Sharding is the process of horizontally partitioning your data across multiple separate machines.
S
22:51speaker_6HOST
You introduce mongos routers, which act like lightweight traffic cops, and config servers, which maintain the metadata map of exactly where every single document lives.
S
23:00speaker_6HOST
So when the application requests a specific document, the mongos router instantly checks the map and routes the query directly to the specific physical shard that holds the data.