When should you shard your database?

episode

The Backend Engineering Show with Hussein Nasser not yet transcribed

▲ 0

Transcript

This episode hasn't been transcribed yet Upvotes decide what gets transcribed next — 0 so far. Sign in to upvote

Related

recent transcribed audio

Trump Makes MAJOR Move as Midterms Get Closer | Guests: Donald & Amy Johnson | 9/29/26 2h 6m · 29 Sep 2026 · The Glenn Beck Program

Best of the Program | Guests: Donald & Amy Johnson | 9/29/26 43 min · 29 Sep 2026 · The Glenn Beck Program

Standoff At Drumcree Enters Third Day 16 min · 29 Sep 2026 · The Last Word with Matt Cooper

The Last Word On Music: Oasis Sell Out Live ’27 Tour In Staggered Three Day Sale 18 min · 29 Sep 2026 · The Last Word with Matt Cooper

The 3 Senate Seats Republicans Can ACTUALLY Flip 1h 2m · 29 Sep 2026 · Next Up with Mark Halperin

Trump Miscalculates as Canada’s PM Carney Plans for US Invasion 16 min · 29 Sep 2026 · Legal AF by MeidasTouch

Report any issue

Source

Recorded28 Apr 2020

Publisheranchor.fm ↗

Handlerec:9886130

Show notes

Database Application level sharding is the process of splitting a table into multiple database instances in order to distribute the load. However, Sharding a database is an expensive operation (maintainability and overhead) and I suggest you do that only when you absolutely need to. That means when your single instance database can no longer serve queries with minimum latency. So I suggest you monitor that and only shard if necessary.. I rather do replication make master / backup and make requests read from replica than Sharding just because it is easier.. good question... nice idea for a video 5:00 Partition horizontally 7:45 Replication (Master/backup) Scale reads 11:00 Scale writes by region 12:30 Sharding 16:40 Sharding in YouTube

Ask this episode

“What did the council decide on item 42?” — answered with the speaker and the moment.

Sign in