# Bo Ingram - How Discord Stores Trillions of Messages (Highlights)  ## Metadata **Review**:: [readwise.io](https://readwise.io/bookreview/62205966) **Source**:: #from/readwise #from/reader **Zettel**:: #zettel/fleeting **Status**:: #x **Authors**:: [[Bo Ingram]] **Full Title**:: How Discord Stores Trillions of Messages **Category**:: #articles #readwise/articles **Category Icon**:: 📰 **Document Tags**:: #work **URL**:: [discord.com](https://discord.com/blog/how-discord-stores-trillions-of-messages) **Host**:: [[discord.com]] **Highlighted**:: [[2026-07-22]] **Created**:: [[2026-07-25]] ## Highlights - In our [previous iteration of this post](https://discord.com/blog/how-discord-stores-billions-of-messages), we mentioned being intrigued by ScyllaDB, a Cassandra-compatible database written in C++. Its promise of better performance, faster repairs, stronger workload isolation via its shard-per-core architecture, and a garbage collection-free life sounded quite appealing. ([View Highlight](https://read.readwise.io/read/01ky5x3vksnfedx78bg87t8cfh)) ^1036598712 - Our data services sit between the API and our ScyllaDB clusters. They contain roughly one gRPC endpoint per database query and intentionally contain no business logic. The big feature our data services provide is request coalescing. If multiple users are requesting the same row at the same time, we’ll only query the database once. ([View Highlight](https://read.readwise.io/read/01ky5xf2xz7ehzpmd15hytfjve)) ^1036600373