Konstantin Gobelyak Email & Phone Number

Created Promo, Producer, Seller, Sections pages based on Search.Also created own deployer for zero downtime deploy with auto change SphinxSearch schemas on all instances and turn on/off PostgreSQL replicas for balancing instances on heavy migrations.Improved and optimized search project:- creating a complex system for typo correction,- set own formula of relevance instead of default bm25- create main-secondary multithreaded replication of plain indexes- decided to move to ManticoreSearch (more stable and under active developing)We also communicated with the ManticoreSearch team about developing a Ukrainian language (lemmatizer), which they developed and optimized for our use.The roots of the SPA came from my team; we started to separate frontend and backend (chose between angular and react, with Angular being simpler), leading to the formation of a frontend team.The company continued to grow, and 2 new services were introduced: user service (PHP, Symfony 4, GraphQL) and user session service (Golang, gRPC with protobuf). One of the user service's components was run in Kubernetes, a first for the company.As the team grew, it was split into two: the first team, named dataKeepers (with me as TL), was responsible for the user service and store service. The second team, named Armory (with its own TL), handled search and user session services.I then became the Lead TL, overseeing 4 teams, and actively participated in the Architecture Board. Its task was to solve services integration problems and introduce new technologies.Later, I helped create a new team (named SEM) that developed SEO functionality, and I was the TL there.At one point, the TL of Armory stepped down to remain in the team as a developer, so I became the TL for 3 teams.We eventually found a new TL for the SEM team, and in the end, I was the Lead TL of 5 teams, personally leading two of them.

Initially, I worked on the admin part, parsing different supplier prices using a custom ETL process. This involved working with PHP, MySQL, MongoDB, and jQuery. I also utilized Gearman for job management.My work on the flight aggregator, Rozetka Travel, was primarily focused on the client side, using jQuery, and included optimizations of the DOM tree, such as hiding and showing elements on scroll.Subsequently, I initiated the "Store" project to transfer data from our partner, OWOX, to our storage. The selection of the database was based on benchmarks among MySQL, PostgreSQL, MongoDB, and Neo4j, with PostgreSQL emerging as the best in our synthetic tests. For the PHP microframework, we chose between Phalcon and Lumen, ultimately finding Lumen to be more user-friendly.Additionally, I started working on a new Search project utilizing Yii2, Redis, and SphinxSearch.