garrettf

4 ms·

1. 1.▲
   by garrettf 5y ago

   Oh yes—this footnote is not knocking non-relational DBs, in fact we have deployed DynamoDB in production for other use cases today. We were on a tight timeline due to impending TXID wraparound. Switching database technologies would have req
2. 2.▲
   by garrettf 5y ago

   Plenty! But not significant compared to page content in terms of storage or load. That unsharded data is stored in separate unsharded databases today, but each table could be sharded later using a different shard key (often user id). Luckil
3. 3.▲
   by garrettf 5y ago

   > Can you share details on the routing? All in the application layer! All of our server code runs from the same repo, and every Postgres query gets routed through the same module. This means that it was relatively easy to add a required
4. 4.▲
   by garrettf 5y ago

   Good question, that was an option. The main motivating factor here was that vacuums were beginning to take dangerously long. O(weeks) to complete, independent of the load on the database. While migrating spaces in segments would have reduce
5. 5.▲
   by garrettf 5y ago

   Howdy all, author here! Sharding our Postgres monolith was a huge undertaking for a small team. We got a huge boost from folks that joined within weeks before the switch-over date. If you’re interested in thinking about problems like this,