THEIR CHALLENGE
Providing key services to both players and clubs
Playtomic is the world’s leading racquet sports community, connecting millions of players and clubs across nearly 70 countries. Founded in 2017, the company provides a dual-purpose platform that offers club management tools alongside a social network for athletes to find partners and book courts.
“We focus on padel, tennis, and pickleball,” said Sergio Moratilla, VP of Technology at Playtomic. ”One of our most successful features is ‘open matches’, which is for people looking for others to play with. When the Playtomic system finds a matching player for you, it then automatically assigns you a court at a local club.”
It’s a platform built on service innovation and rapid responses, but the rigid schemas and complex data-definition requirements of its previous relational database were hampering Playtomic’s evolution. Updating features like automated matchmaking and levelling for players, or price setting and membership management for clubs was fraught with risk and required time-consuming backward compatibility checks.
“When you develop on a relational database, it usually involves a schema change beforehand,” said Moratilla. “Deployment then becomes a critical moment because changing a huge table in a production system has such significant consequences. We saw that deployment would be so much faster without this.”
As Playtomic grew, users increasingly relied on natural-language search to find clubs by name or location, driving the need for a separate search system alongside the main database. While this improved the user experience, it added operational complexity. Spikes in activity required manual scaling, and limited visibility made it hard to identify inefficient queries, forcing the engineering team into reactive infrastructure decisions during a period of rapid growth.
“Our core business isn’t about building infrastructure, it’s providing services to players and clubs,” added Moratilla. “We quickly realized that we didn’t want to maintain the system we had set up, and that we wanted to move it to the cloud.”

