Vinted Architecture: Keeping a busy portal stable by deploying several hundred times per day
Monday, February 9, 2015 at 8:56AM
Todd Hoff in Example

This is guest post by Nerijus Bendžiūnas and Tomas Varaneckas of Vinted.

Vinted is a peer-to-peer marketplace to sell, buy and swap clothes. It allows members to communicate directly and has the features of a social networking service.

Started in 2008 as a small community for Lithuanian girls, it developed into a worldwide project that serves over 7 million users in 8 different countries, and is growing non-stop, handling over 200 M requests per day.

Stats

Technology Stack

Third party services

Core app and services

Data warehouse stack

Servers and Provisioning

Monitoring

Architecture overview

Team

How The Company Works

Development Cycle

Avoiding Failures

Deploying hundreds of times per day does not mean everything always has to be broken, but keeping the site stable requires some discipline.

Reducing Time To Production

There is a big focus on both fast and stable releases, the team is always working to keep build and deployment times as short as possible.

Running live database migrations

We can change the structure of our production MySQL databases without downtime, in most cases even at rush hour.

Operations

Server Provisioning

Monitoring

Chat Ops

Data warehouse stack

Lessons Learned

Product development

Infrastructure and Operations

Data warehouse stack

Article originally appeared on (http://highscalability.com/).
See website for complete article licensing information.