How Trendyol’s Database Team Scales for 200K Merchants and 1M+ Orders a Day

The Customer

When Demet Mutlu founded Trendyol in 2010, few could have predicted the meteoric rise that would transform this modest Turkish fashion startup into the country’s e-commerce juggernaut. The journey accelerated in 2018 when Alibaba Group became a major shareholder, injecting both capital and technological expertise.

Fast forward to today, and the numbers tell a remarkable story. By 2023, Trendyol was generating a staggering $4 billion in revenues, commanding the Turkish e-commerce market with a particularly dominant presence in fashion — capturing nearly half of all online sales in that category alone.

A Digital Retail Powerhouse

Behind these impressive figures lies a platform that has become indispensable to Turkish consumers and merchants alike. With over 40 million active customers and 150+ million monthly web visits, Trendyol has captured approximately 50% of Turkey’s online fashion market and an even more impressive 70% of online beauty sales.

But Trendyol isn’t content with being just a fashion destination. They’ve expanded their horizons to offer everything from electronics to home furniture, cosmetics, and beyond. Along the way, they’ve become a vital partner for more than 200,000 independent traders and SMEs, delivering over a million packages daily to doorsteps across Turkey.

This explosive growth brought its own set of challenges, particularly for the technical teams responsible for keeping Trendyol’s digital foundation rock-solid while scaling to meet ever-increasing demands.

The Challenge

Every e-commerce platform lives or dies by its technical infrastructure, and for Trendyol, database reliability is essential. As transaction volumes soared and customer expectations rose, their database team found themselves facing a complex puzzle.

First came the geographical challenge: how to create and manage database deployments across multiple regions — specifically Istanbul and Ankara — to ensure customers would always have a responsive experience regardless of their location. These deployments needed iron-clad resilience against infrastructure problems, which sometimes meant dealing with provisioning processes that could stretch from hours into days or even weeks when underlying technical issues arose.