Anton Morev

Anton Morev

Wormsoft, CTO

Moscow, Russia

My name is Anton Morev. I am the founder of Russian company Wormsoft.ru. We are creating complex systems of business process automatization.

My commercial development begins in 2008 - Creating trading bots for Moscow Exchange. In web develop I am since 2011.
Despite the fact, that I am founder and leader of our develop command, I don't stop to investigate progress in development and create apps for out clients, when it can be done by new technology and I can integrate new technology in our business product and make new product from it.

I have experience as a speaker on Russian conferences - https://amorev.ru/en/conf-talks/. Here is the list of it.

Area of Expertise

  • Information & Communications Technology


  • Web
  • Web Development
  • Mobile Development
  • PHP
  • Yii
  • Yii PHP Framework
  • Vue Js
  • Web Frontend
  • Web Backend

Shifting away from PHP to GoLang using real examples

We at our company have been busy “preparing” PHP for serious tasks for a long time and have achieved some success in this. But time does not stand still, just like customer requests for the dynamism of their applications. The scale of one project required the “cut” into microservices, and then we learned both different new technologies (GraphQL, GRPC, Kubernetes, etc.), and new languages for us in the backend world – JavaScript and Golang.

Это изображение имеет пустой атрибут alt; его имя файла - switching-from-php-to-go-1024x516.jpg
Subsequently, we began to program backend using Go and JS more and more, so that introduced us to a completely new world of opportunities and difficulties 🙂 On my presentation I plan to talk specifically about the features of the transition from PHP to GoLang, namely:

* Comparison of Asynchronous Features
* How to start programming in Go if no one in the team has previously used Go
* How to make the transition as cheap as possible for the company
* Where and what everyday tasks are easier to solve
* In what situations, which language is more suitable and why?

History of one PWA

For a long time it became possible to turn WEB applications into “progressive web applications” and get an application, in some cases, not inferior to real native applications. PWA, at first glance, looks like a very logical solution. It is obvious because it is much cheaper and easier to make an application that will work immediately on all the platforms where there is a browser. Since mobile phones are our constant companions and, very often, PWA capabilities are enough and it is not necessary to make a native application, the report will be useful for everyone who, in one way or another, works in WEB applications and considers the movement towards application development specifically for phones. Questions that I am ready to disclose in the report:
* What PWA is and what opportunities it opens
* PWA Implementation Basics
* Known and Unobvious PWA Issues
* PWA Development Case Study Step-By-Step
* When it’s worth to start with native development right away

Organization of cropping images on the fly and their optimal and scalable storage

What if the same picture is needed in different sizes, different quality and different formats for each device?
Where and how to store pictures so that it could be advantageous and cheap?
How using nginx and backend logic organize the efficient preparation and storage of images for different devices and formats?

Having made a lot of mistakes, we came to a solution that we are actively and successfully using in current production projects.

As an example, I consider the implementation of an extensible file storage on the backend and the example of integration with this storage on the JS side of the Vue + Nuxt.JS framework.

Transition from REST API to GraphQL using real projects as an example

Dreaming of unloading Backend developers as much as possible, I decided to try to delegate the logic of grouping data in server requests to Frontend developers. GraphQL was chosen as the final solution. First, we made a couple of test projects on it and, after the checks, we started using GraphQL in customer projects. A lot of water under the bridge and knowledge about the features of the translation which could be shared has accumulated. In the process of transition, we encountered many features of this technology and the experience gained, at the moment, allows us to reveal the following points:

* Pros and Cons of Switching to GraphQL
* How to gradually switch to GraphQL
* How to safely delegate data assembly logic to Frontend
* How you can get the maximum effect from connecting GraphQL to a project with microservices
* The disadvantages of technology that we realized only when we had faced with them
* What you need to know in order not to shoot yourself in the foot while connecting GraphQL

GDG DevFest Warsaw&Radzymin 2019

December 2019 Warsaw, Poland

Anton Morev

Wormsoft, CTO

Moscow, Russia