The outcome
So how did it go, betting on Aiven? After three years, Mirakl are more than happy. They are seeing multiple benefits from using Aiven for Apache Kafka, as opposed to setting up their own Kafka cluster. One big advantage is of course the fact that Aiven handles all the management and upgrade tasks.
“It’s critical for us to have our developers focused on delivering value, instead of struggling with operations,” Nagi says. “To put it bluntly, we’re an e-marketplace company, not a Kafka maintainer.”
Mirakl are also discovering that their time-to-market has been greatly reduced. The reason lies very much at the grass root level. A monolithic application has a single codebase, which limits the number of developers or teams who can work on it concurrently. With microservices, teams can work on different parts of the system at the same time. This cuts down on development time and increases the agility of the business.
At first glance, using a managed service looks more expensive than a self-hosted cluster. But after you add up the maintenance, support and connector development costs, and add the constant concern of keeping your critical resources onboard, the total cost of ownership is actually much lower.
Mirakl are currently running about 100 servers and tons of microservices; Kafka processes some 9000 messages every second. This means upgrades are a headache, but they’re no longer Mirakl’s headache.
“Thanks to Aiven, the time our teams used to spend on running Apache Kafka can instead be poured into our core business. We’ve found exactly the partner we were looking for. They take care of the infrastructure securely and reliably, but we still hold the keys to our own data.”