“We ended up re-sharding a bunch of our data to be, um, fetchable by channel ID rather than by team ID. And then that allows for much better horizontal sharding structure as well.”

The Pragmatic Engineer · Scaling Slack and GitHub with Maude Lemaire

Play from 51:00
51:00

Audio streams from the publisher’s own feed. Verbatim does not host or copy it.

What was described

re-sharded Slack data from team-level to channel-level keys to achieve finer-grained horizontal scaling

Said nearby on the same subject

“I also built a kind of custom game server that scaled horizontally. You can just add nodes.”
DW
Dominic Williams
The Enterprise AI Show ·
Why it worked Share this moment
“We believe that hardware needs to be built in-house… scaling human data is extremely important… other companies bet on scaling robot data only”
♫
Said on Latent Space: The AI Engineer Podcast
Business model Share this moment
“You're now aggressively scaling up your self-serve capabilities to give enterprise agencies the keys to the kingdom so that they can do stuff themselves, get curious, get inquisitive, get ROI measurement”
♫
Said on The CPG Guys
Why it worked Share this moment
“For communication, they message me in Slack, I don't have notifications turned on. So I never see them. And I only go into Slack once a day to check in with them.”
CJ
Christy Johnson
The Dream Biz® Podcast | Anti-Hustle Business Strategies for Creative Entrepreneurs ·
How they work Share this moment

Moments like this, every Monday

The strongest new moments on your topics, in the speakers' own words. Free for three topics.

No card. No password. One-click unsubscribe.

Track a competitor?

Pro watches up to 25 names or phrases and emails you the morning after they are said.

See Pro, $29 a month

Verbatim quotes a short extract and links to the episode; the episode belongs to its publisher. Remove a show.