Scaling a Music Bot: Sharding Explained

Here's the constraint that shapes every large music bot: a single Discord bot account can hold only one voice connection per guild. To play music in many channels across a huge number of servers, you need multiple instances.

Sharding uses discord.js's ShardingManager to spawn one process per shard. Each shard owns a slice of your servers and its own voice connections. One shard crashing never takes the others down — respawn is on.

The instance lock is shard-aware: each shard gets its own lock file so they never block each other. Command deployment only runs on shard 0, and the presence line keeps its live guild count across the whole fleet.

One honest warning: large fleets need storage that can handle concurrent writes — the bot warns you at startup if your setup isn't sharding-ready, so the only mistake you can make is one it tells you about.