Design Discord's Message Storage/Playground
Storing trillions of chat messages
Click a part to change it, put something in front of it, or kill it. Turn the traffic up. Every number moves as you go; nothing is graded. About 120 million messages a day with reads roughly equal to writes; the peak and ten recipients per message are assumed.
Running
- Requests failing
- 0%
- Backlog growing
- none
- Instances running
- 45
What goes through it
| Operation | Offered | Outcome | Wait | Up |
|---|---|---|---|---|
| Messages sent | 4,170/s | All served | 109 ms | 99.999% |
| Message reads | 4,170/s | All served | 104 ms | 99.999% |
| Live deliveriesbackground | 42k/s | Keeping up | – | – |
Wait is the expected time a caller waits; Up is the share of time every part it waits on is running.
What your changes did
Nothing yet. This is the reference design: change something to see what it buys and costs.
At this traffic
Everything is running within capacity.
Ask AI what your design does
AIThe numbers above come from a simple model. The AI reads your design, what you changed and these numbers, and explains where it holds and where it fails, citing how the engineers who built it did it. It can be wrong.