The Fleet Architecture
Poolki Music is not just another standard Discord bot, it's a highly scalable distributed music ecosystem. Instead of relying on a single monolithic instance that gets rate-limited or overwhelmed, Poolki operates as a load-balanced fleet of bots.
Currently running 5 public bots (with auto-scaling capabilities as usage demands), the system provides a seamless, zero-friction user experience. You use one unified prefix (default: p!, fully customizable), and a single master controller handles the text interactions. The moment you trigger a play or join command, the backend intelligently routes the request and dispatches the first idle bot directly to your Voice Channel.
Under The Hood
Engineered for high availability and zero latency, the infrastructure relies on a robust backend stack to manage cross-bot synchronization:
- JDA (Java Discord API): The core wrapper handling websocket connections and multi-shard Discord REST API interactions.
- Redis: The backbone of the fleet. It handles cross-process state synchronization, keeping track of which bots are idle, which are streaming, and ensuring commands don't collide.
- PostgreSQL: The persistent relational database managing guild configurations, custom prefixes, and user preferences.
- LavaPlayer: The raw audio engine powering the extraction, decoding, and streaming pipeline.
Universal Streaming Support
Music doesn't live on just one platform. Poolki natively extracts and streams high-quality audio from a massive array of sources, bypassing traditional limitations:
- Spotify & Apple Music
- Anghami & Deezer
- SoundCloud & Tidal
- YouTube Music & Twitch
- And many more...
Initialize The Fleet
Bring the ecosystem to your server. Join the Support Server to track the project, or invite the bots directly to your guild:
