Sergey Gordeev

Senior Software Development Engineer at 8bit group
  • Claim this Profile
Contact Information
us****@****om
(386) 825-5501
Location
Moscow, Moscow City, Russia, RU

Topline Score

Topline score feature will be out soon.

Bio

Generated by
Topline AI

You need to have a working account to view this content.
You need to have a working account to view this content.

Experience

    • Russian Federation
    • Internet
    • 1 - 100 Employee
    • Senior Software Development Engineer
      • Nov 2019 - Present

      - The construction of models and algorithms for determining similar names of brands and products for combining into one; - Creation of a task manager for processing event queues (sending letters after registration), pending tasks (checking the success of payment), and scheduled tasks. The task manager read the tables and, depending on the type of task, passed it to a specific worker for processing, periodically polling their status; - The construction of models and algorithms for determining similar names of brands and products for combining into one; - Creation of a task manager for processing event queues (sending letters after registration), pending tasks (checking the success of payment), and scheduled tasks. The task manager read the tables and, depending on the type of task, passed it to a specific worker for processing, periodically polling their status;

    • Back End Developer
      • Feb 2017 - Oct 2019

    • Full Stack Engineer
      • Jan 2015 - Jan 2017

    • Russian Federation
    • Technology, Information and Internet
    • 1 - 100 Employee
    • Senior Web Developer
      • Jan 2012 - Dec 2014

      PHP 7.2, Phalcon, Elasticsearch, MariaDB, Redis, Docker, Kubernetes, Prometheus, Grafana, elk, VueJS Skidex.ru is a marketplace (product aggregator) written in PHP using the Phalcon 3.4 framework. The stack consists of PHP7.2, MySQL, Redis, Elasticsearch, Prometheus, Gitlab CI \ CD, kubernetes, docker. Deploy takes place in one click. The backend served three clients: Android and iOS went to the API, the web partially went to the API, partially took data from pages rendered by the backend. Mobile and web clients used different APIs. In my opinion, supporting both of them was difficult, so I promoted the idea of switching to a JRPC protocol with a common API for all clients. At the beginning, clients sent a start-up message, according to which later we could give different answers within the framework of one method. All changes went through versioning. Show less

Education

  • Ryazan State Radiotechnical University (former Academy)
    2012 - 2016

Community

You need to have a working account to view this content. Click here to join now