# Overview While [[Partitioning]] splits tables within a single database, sharding splits data across multiple database servers. # Key Considerations ## Sharding Strategies #flashcard - Application-Level Sharding - handle sharding within the application - Pros: - Simple to understand and implement - Complete control over sharding logic - Can use standard PostgreSQL features - Cons: - Need to handle cross-shard queries in application code - More complex application logic - Have to manage multiple database connections - Geo-based Sharding - Range-based Sharding - Hash-based Sharding <!--ID: 1751507776911--> # Implementation Details # Useful Links # Related Topics ## Reference #### Working Notes #### Sources #### Topics to Cover - Strategies #### Related Topics -[[ Hoy Key / Celebrity Problem]]