---
title: "Discussion on \"How Figma, Notion and Slack handled sharding\" | Hashnode"
description: "Discussion on \"How Figma, Notion and Slack handled sharding\". Horizontal sharding is the move every team hopes to put off. You take one database, split its rows across many, and suddenly every query, migration and on-call runbook has to know where the data lives"
url: "https://hashnode.com/posts/how-figma-notion-and-slack-handled-sharding/6ad66801a77afd9d690ff4fa"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How Figma, Notion and Slack handled sharding](https://howtheyscaled.hashnode.dev/how-figma-notion-and-slack-handled-sharding?utm_source=hashnode&utm_medium=feed)

Horizontal sharding is the move every team hopes to put off. You take one database, split its rows across many, and suddenly every query, migration and on-call runbook has to know where the data lives

Oct 19 · 5 min read · howtheyscaled.hashnode.dev  
Read the article

-   [#database](https://hashnode.com/tag/database)
-   [#sharding](https://hashnode.com/tag/sharding)
-   [#scalability](https://hashnode.com/tag/scalability)
-   [#architecture](https://hashnode.com/tag/architecture)

## Written by

[How They Scaled](https://hashnode.com/@howtheyscaled)

@howtheyscaled

  
[View profile](https://hashnode.com/@howtheyscaled)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
