Semën Samusev Email & Phone Number

Moscow, Ru

It is a completely different journey - leading and managing a distributed team of backend developers while keep being responsible for high level technical decisions (including but not limited to backend systems architecture, tech stack, servers' infrastructure). Conducting interviews, team motivation, carrying people training and personal growth - all this stuff.Also as a technical lead I designed (and implemented core components of) distributed architecture for Bullet Echo - real-time PvP stealth shooter, which is the most sophisticated Zeptolab's game at the moment. Backend infrastructure of Bullet Echo consists of 8 different (micro)services on more than 170 bare-metal servers across 6 geographical regions and could handle up to 250K concurrent players.

Have you ever played *King Of Thieves*? If not you definitely should :) So I'm the guy who has designed and implemented a scalable back-end server infrastructure for this game that supports 170k concurrent players online. I've also implemented the core game logic on server-side. Moreover I participated in designing architecture for our other hit - C.A.T.S (real peak numbers - 250K concurrent players and 80K requests per second). You can find me in credits of Cut The Rope 2 (for Android) too - I've implemented a pretty simple backend for this game.It's also worth saying that I * have developed and implemented CI/CD processes on all projects;* started technical knowledge sharing culture in the company;* was involved in the development of several game projects that weren't released =(Main Technologies and Frameworks: Java, Kotlin, Netty, Spring (core, security), Redis, Cassandra, PostgreSQL, Zookeeper, Kafka, Hazelcast, Docker

Москва, Россия

This is the place where I had my first experience in building a scalable cluster solution from scratch. It was a massive National Healthcare System consisted of many connected functional modules and each of them could be deployed autonomously on a different server. In addition, it was my first night with nosql databases. In Medlinesoft I also acted as a team-lead by establishing technologies and frameworks to meet the main system requirements as well as coordinating remote teams, reviewing code, evaluating candidates and conducting technical interviews.Main Technologies and Frameworks: JGroups, Spring (core, security, integration), JPA+Hibernate, Apache Tapestry, MongoDB

Moscow

There I had a great experience in developing the high-performance low-level network application designed to gather tons of realtime data through TCP and UDP from a various terminal equipment installed along the Ring Road of St. Petersburg (videocameras, weather stations, road sensors, traffic signs, etc). After aggregating this data is sent to the main frontend system managing the road traffic. Also I rewrote some core functional of that system and made some architectural changes to improve scalability and reliability.Main Technologies and Frameworks: java.util.concurrent, NIO, JBoss Netty (Apache MINA), JMS, Spring (core, security, integration), JPA+Hibernate

Moscow

M-Commerce was a much more interesting and challenging place than before (but it was still close enough to bloody-enterprise). There I got my first independent decision making experience, had a lot of fun and designed and developed a pretty easy (it didn’t seem so easy at the time) backend for online processing of customer purchases via cellphone. I also developed an internal web-portal with the purpose of holding and processing payment documents, collecting and showing statistics, interacting with trading partners, etc. Main Technologies and Frameworks: Servlet, JSF, Web-Services, Spring (Core + Security), JPA+Hibernate, JMS, Apache Camel

Moscow

There is not much interesting to tell about. My work here was a boring 3-tier enterprise solution for corporate user profiles management based on Oracle IdM. Blah. Because it was my first commerсial work experience I’ve already forgiven myself for that.Main Technologies and Frameworks: JDBC, Hibernate, JNDI