Route GORM database operations to shards for PostgreSQL and MySQL tables.
npx skills add https://github.com/liurida/gorm-development-skill --skill gorm-sharding
Please help me install this Agent Skill. Skill: gorm-sharding Source: https://github.com/liurida/gorm-development-skill/tree/main/sharding Command: npx skills add https://github.com/liurida/gorm-development-skill --skill gorm-sharding
The GORM sharding plugin routes database operations to the correct physical shard for horizontally partitioned tables, preventing ambiguous queries, failed operations, and inconsistent primary key generation across distributed datasets.
Register the GORM sharding plugin with ShardingKey set to user_id, choose NumberOfShards, create the per-shard tables, and then run your normal Create/Read/Update/Delete operations including the sharding key.
High-intent search queries and answers about installing and using this skill.
To scale PostgreSQL horizontally with GORM, register a sharding plugin with a defined ShardingKey and NumberOfShards, pre-create per-shard tables, and use shard-aware primary keys like Snowflake to route create, read, update, and delete operations to the correct physical shard.
You must include a sharding key in GORM queries to determine the target shard for horizontally partitioned tables. Omitting the sharding key from WHERE clauses prevents the plugin from routing the operation and triggers an ErrMissingShardingKey error.
You cannot use auto-increment IDs for primary key generation across MySQL shards because they cause inconsistent IDs across distributed datasets. You must use a shard-aware primary key generator such as Snowflake or PostgreSQL sequences to provide globally unique IDs.
GORM sharding supports custom routing algorithms for complex data distribution by allowing user-defined sharding algorithms alongside default modulo-based routing, intercepting and rewriting GORM queries to target shard-specific tables based on your custom rules.
Limitations of horizontal sharding include avoiding cross-shard joins by design and the requirement to pre-create per-shard tables. You must also consistently include the sharding key in operations to prevent ambiguous queries and failed database operations.
The best way to route database operations to appropriate shards is using a GORM plugin-based interception mechanism that rewrites queries to target shard-specific tables, requiring a defined ShardingKey and NumberOfShards to distribute records like an orders table across 64 shards for improved write throughput.
heinschulieProvision managed PostgreSQL, Redis, MySQL, and MongoDB databases via Railway templates.
AugustEmnaQuery and modify data across integrations and warehouses via chat.
Penitence1992Generate and parse Snowflake IDs with embedded business type and index.
gmcabritaEnable horizontal scaling for Postgres databases with PlanetScale-managed sharding.
