Да все их любят! Приходите слушать про бекенды!
Мои контакты для любых вопросов:
Any large company at the implementation of a web-project should in some way integrate it with internal accounting systems. Each integration of this kind implies tight interaction between a contractor for the development of the client side with customer IM IT and contains a lot of non-obvious risks. In the report we will cover the following poins:
- Work at large integration projects. Where to start and how to finish;
- Technical documentation on the project: what, who and when;
- Problems of web services, methods of response and ways to eliminate them.
- Project infrastructure: typical layout of system components.
In the report we will tackle what kind of beast this "Monad" is, and where the beautiful pure world of mathematics breaks down on the peculiarities of programming languages.
I joined Lazada 2 years ago, when the first
steps towards the microservice architecture were made, but we were still at the
very beginning of the journey. During this time, we went from 5 to 60
microservices, written on Golang, bumped heads and gained experience, which I want to share
I want to talk about how we solved
operational problems, such as unified deployment, collection of logs and
metrics, request tracking, etc.
And the most important thing, as we
understood it, is that all micro-applications work according to the general
plan and our architecture works the way it was intended.
My report will be interesting to you if you
are thinking of starting to build something based on microservice architecture,
looking for the ways to solve
operational problems or just are interested in the topic of microservices.
Distributed systems have several fundamental properties that prevent us from thinking about them in the usual way. I will try, with the example of several basic distributed algorithms, to demonstrate these differences from traditional ‘monolithic’ systems.
I'll tell you about OpenSource. What it really is, how I got there, and what has changed comparing to the time I have not got there yet. About problems, fear and hatred, the dissatisfied, time and money.
In this report, I want to highlight the following aspects of development in Golang language:
- Dependency Management
-Static code analysis
-Performance of Golang applications
-Recruitment of Golang programmers
The global demand for Japanese goods is consistently high; however, the Japanese sites overall do not traded outside the Japanese market due to transaction, delivery and payment problems. 10 years ago, inJapan service was settled to solve this problem, and we will tell you what difficulties had to be encountered in the course of the technical implementation and automation of the site annually sending over 100,000 packages around the world.
- Automation of search against the major trading sites in Japan
- Implementation of an automated transaction management system
- Automation of inventory control
- Implementation of the micro-service architecture of the project
- Automation of interaction with the mail of Japan through simulation of user actions
- Automation of the payment system and online supplier transactions processing
What if you need to make a fast and not too complicated service, which well-scaled vertically?
How to avoid unnecessary external queues on redis?
How to do without gunicorn?
How to fit everything into one process?
I'll explain all this with the example of building API Gateway on Python, Flask and Gevent.
В этом докладе я расскажу, как мы в Почте@mail.ru разрабатывали и внедряли новую систему хранения аттачей из писем. Доклад состоит из трех частей. 1. Я расскажу, как построить систему, которая принимает 80 000 файлов в минуту, на лету вычисляет дубли и сохраняет их. 2. Как для этого организована система хранения метаинформации, чтобы на нее хватило оперативной памяти. 3. Какие нужны инструменты для обеспечения своевременного нахождения проблем в холодных данных. Жесткие диски, к сожалению, не вечны, а данные пользователя терять нельзя.