Vertical Sharding Sucks
a year ago
- #postgres
- #database
- #sharding
- Vertical sharding reduces load on the main database but complicates the application architecture.
- Vertical sharding decreases uptime because multiple databases must be operational for the app to function.
- Application-layer joins become necessary when tables are split across databases, increasing complexity and potential for bugs.
- Vertical sharding can lead to duplicated data and increased latency as developers try to work around the limitations.
- The Postgres ecosystem lacks a built-in OLTP sharding solution, unlike MySQL with Vitess or DynamoDB.
- PgDog is an open-source project aimed at providing a sharding solution for Postgres to improve productivity.