Ama. Avito. Backend

Hello! As promised, today we are ready to answer questions about the Avito backend, the development of the server part in general, and about high loads in particular. How does it work with a site that almost a quarter of Russia's population visits every month? Ask us! We will answer from 12 to 19 hours Moscow time. Under the cut, I represent six of my colleagues who will be in touch with you today and remind you of possible topics of dialogue.

AMA!
UPD, 19:03 Moscow time: Thank you all for the questions!
Officially, we end the AMA and say goodbye, but if possible we will respond to comments.

Vitaly Leonov, vleonov
Head of the server side development.
In Avito 5 years, he started as a backend developer, now he is responsible for all server development.

Victor Announcer, Rpsl
Techlide in unit monetization. Over 10 years experience in website development. In Avito, he is responsible for the cross-platform development team in one of the monetization units.

Nikolay Balakirev, madfaill
Lead developer of the server part, Avito.Pro technical unit. Responsible for Avito services for professionals: ActiAgent , ActiDealer , Avito PRO. He can also be addressed questions about the service Autoteka .

Igor Somov, Cubist
Lead server side developer. In Avito 2 years. Works in moderation unit, deals with several internal projects.

Andrey Smirnov, martovskiy
Lead server side developer. Prior to Avito, he worked at Playfon and Sotmarket - everywhere there were high loads and high demands on system reliability. Engaged in statistics, search and deploy. Avito works on search engines so that they work quickly, accurately and reliably.

Sergey Orlov, marrrvin
Server side architect Unit Leader Architecture. In Avito more than two years. He is engaged in the development of the backend architecture, collecting and implementing the best practices. Builds an internal PAAS. He can answer questions related to the cloud infrastructure in general and Kubernetes in particular, Continuous Integration, Delivery and Deployment, using the microservice approach in the company.

Possible topics:

• device of our internal projects;
• success stories and failures;
• high loads and that's it;
• what we saw in PHP, and why we use Go and Python;
• how our search on Sphinx works;
• Infrastructure, Kubernetes, Continuous Integration, Delivery and Deployment;
• and so on.

We are waiting for your questions, stories and clarifications. If you want to get a guaranteed answer - write a request in the comments of the first level. Go!