Discortics
How a personal Discord bot grew into a platform serving millions — and the scaling journey from a single monolith to a Go-powered microservices architecture.
Born From a Personal Need
Discortics started as a small personal automation project — a bot built to help manage the founder's own Discord server. A few interesting features were added, people started liking it, and the question came naturally: why not make it public? People would love to use it. And that was how Discortics was born.
It launched as a small Discord bot serving its first hundred clients — completely free, positioned as a free alternative to all the paid giants in the industry. There was no funding. The founder was still a student. But there was a creative hack: he approached a small startup that was providing VPS services for Minecraft creators and Discord bots, and offered them advertising in exchange for a small server to host the bot. That was all it took to get started.
Organic, Then Explosive
The bot grew organically. People loved it for its UI-centric approach — we always preferred it to be easier to use, a beauty to the eyes, rich in functionality without overcomplicating things. That design philosophy set Discortics apart from everything else on the market.
Our first premium client actually approached us — they asked whether we had premium plans at all. They wanted something custom-branded for their own community, their own identity and branding. That's how premium plans were born, and from there it grew spontaneously.
As revenue came in, we started advertising on the right mediums to draw customers properly. We also went back to the startup that gave us that initial server — thanked them, paid them out generously, and even helped them out financially during a difficult period as gratitude for that early boost.
The Scaling Journey
The Monolith
A single monolithic application handling all REST endpoints, Discord events, and caching. Everything ran in memory with MongoDB as the datastore. Each premium customer was hosted in a separate Docker container with differentiated hosting — if the public free version went down, premium instances stayed up.
Horizontal & Vertical Scaling
As the free bot grew to handle 5 million simultaneous active users while processing massive amounts of statistical data, we scaled using Discord websocket sharding and clustering across multiple servers to split the load. But the number of Docker containers for 700+ premium customers and memory usage exceeding 256GB pushed this approach to its limits.
Microservices Architecture
The current architecture — a full microservices rewrite with RabbitMQ as the message broker, split into three core services: a REST Gateway written in Go acting as a multiplexed proxy layer to Discord with multiple IPs and bucket-based rate limit management; a Gateway service also in Go capable of managing multiple bot connections simultaneously, eliminating the need for a container per bot; and an Event Handler for processing Discord events efficiently. Minimal resource footprint, maximum throughput.
What We Built
What It Meant
Discortics proved that a student with no funding could build and scale a consumer platform competing with established, well-funded players. From a bartered VPS to a Go-powered microservices architecture handling millions of concurrent users — every constraint forced a better engineering decision.
The infrastructure patterns, the scaling discipline, and the product instincts developed during Discortics now power everything Vexvo builds — from enterprise systems to the ventures we're launching next. Discortics wasn't just a bot. It was the foundation that built the company.