The Pragmatic Engineer
The Pragmatic Engineer

Scaling Slack and GitHub with Maude Lemaire

November 5, 2026

AI Summary

5 min read

Maude Lemaire spent eight years at Slack, worked on database scaling at GitHub, and improved time-to-first-token at Cursor. She is also the author of Refactoring at Scale. In this conversation, she walks through the messy, high-stakes reality of scaling products millions of people use daily — from load-testing Slack with 500,000 WebSocket connections to untangling GitHub's Rails monolith and its 16 database shards for all pull requests and issues. The thread running through it all: scaling is as much about product judgment and organizational dynamics as it is about engineering.

The Cost of High-Fidelity Load Testing

When Slack needed to prepare for a customer with 500,000 users (likely Amazon), the engineering team knew the existing load-testing approach was inadequate. Previous tests only measured API throughput and database load, but the real scaling problems came from WebSocket connections — the stateful links that deliver messages, notifications, and emoji reactions in real time. Without active WebSocket connections, you cannot simulate the cascading effects of a "thundering herd" (e.g., a CEO announcing a day off in a 100,000-user channel, triggering thousands of simultaneous emoji reactions that fan out to everyone).

Continue reading the full summary in the app — free to try.

Read Full Summary →

Free • No credit card required

What you'll learn

  • 1 (00:04) **Scaling Inside Slack and GitHub** - Maude Lemaire introduces her experience scaling Slack, GitHub, and Cursor, and sets up the episode's focus on practical scaling challenges.
  • 2 (02:16) **Early Exposure to Computers** - Maude describes her childhood introduction to computers and her unexpected path into software engineering.
  • 3 (06:39) **First Job at Rent the Runway** - Maude explains why she joined Rent the Runway and how it combined her interests in programming and fashion.
  • 4 (09:57) **Early Performance Work at Slack (2016)** - Maude describes joining Slack when it struggled with large channels and the nature of early performance problems.
  • 5 (13:09) **Slack's Original Architecture** - Maude explains Slack's team-sharded architecture and how it broke down with enterprise customers.
  • 6 (17:41) **The Three-Table Problem** - Maude details the challenge of migrating from three separate channel tables (public, private, DMs) into one.
  • 7 (21:22) **The Migration Strategy** - Maude describes her careful approach to migrating the data layer without optimizing prematurely.

+ Full timestamped outline available in the app

Show Notes

Brought to You By:

• Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages.

• turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable.

• Entire – The Git forge for agent-human collaboration. Built for the scale and throughput of agentic coding.

—

What is involved in scaling up large, popular products at places like Slack and GitHub? 

We get an insider’s view on this from Maude Lemaire, a principal engineer and author of ‘Refactoring at Scale: Regaining Control of Your Codebase.’ She spent nearly eight years at Slack, where she led the backend performance infrastructure team, before joining GitHub to tackle database scaling challenges. Most recently, she worked on improving performance at Cursor – including time to first token.

In this episode of The Pragmatic Engineer, Maude and I dig into the challenges of scaling some of the world's largest software products. We explore how Slack handled growing numbers of enterprise customers, how it evolved its approach to load testing, and the lessons Maude learned during nearly eight years of scaling Slack's infrastructure.

She also tells us what it was like joining GitHub in 2024 when Copilot was taking off, the challenges of working with GitHub's gigantic Rails monolith, and how Maude uses AI in her work – while keeping judgment calls and decision-making firmly in her own hands.

Timestamps

00:00 Intro

03:15 Early years and path to software engineering

07:32 First job at Rent the Runway

09:17 The HipChat data leak

10:54 Joining Slack and the challenges of scaling

26:30 Load testing and thundering herds

32:29 Event floods

38:30 Evolving load testing at Slack

48:38 Joining GitHub in 2024

56:52 The challenges of the Rails monolith

1:02:26 How Maude uses AI

1:12:40 Advice for engineers interested in product/platform work

—

The Pragmatic Engineer deepdives relevant for this episode:

• Real-world engineering challenges: building Cursor

• The Pragmatic Engineer