Mitap JavaJam. Javista dispute, log rafting, experiments and microservices

Java developers are cool.

The front-tenders praise them and adopt useful tools , designers bring with special love models, and testers rejoice because everything is automated and life is sugar (but we haven’t told about this yet).

Sometimes we hold java-mitapes for them - we collect experts and ask them to tell something more closely. So this time - colleagues from Sberbank, Odnoklassniki, Yandex and Yandex.Money came to JavaJam and immediately posted a bunch of details about their work.



Under the cut:

- The main thing about logging Java applications using examples from Yandex;
- Development of a tool on Low-code for UFS Sberbank;
- Automation of experiments in Odnoklassniki with the help of Kotlin DSL;
- As in Yandex. Money, we made one platform for microservices instead of seven.

And there is a survey about whether it is appropriate to call java-developers javistami.



When the word game comes to a new level

Guide to rafting on logs (Vladimir Krasilshchik, Yandex)

Important concepts and pitfalls of logging Java applications using examples from the Yandex developer. We will talk about the main concepts in logging Java applications, without which no developer can survive.

I will give examples of unexpected application behavior due to the intricacies of logging from my own practice, and you will learn how to make life with logs easier and more fun - as much as possible. The purpose of the speech is to share practices that will allow you to forget about logging and do some really interesting things.

Model-Driven DevOps (Denis Vasin, Sberbank)

You are probably familiar with DevOps culture, which brings together specialists in development and information technology services (Developement and Operations). But few have heard of the Low-code platform - it turns participants in related projects into Citizen Developers.

In the report I will talk about the development of a tool for Sberbank's Low-code for UFS (Unified Front System). And answer the questions that usually arise from MDE-managers. For example, how to manage versions of models, split generated and handwritten code, or integrate your own tool into standard DevOps infrastructure.

Automation of experiments using Kotlin DSL (Alexander Tarasov, Odnoklassniki)

In a large project, you cannot simply take and make a feature available to all clients. For a smooth start, we conduct experiments that require manual changes — and often this leads to time costs and errors. To get rid of them, we decided to automate the preparation and launch of experiments.

In the report, I will tell you why we wrote custom DSL and how Kotlin helped make it compact and convenient. And also about what problems need to be solved, so that everything works, as you planned.

Unified microservice platform Yandex.Money (Vasily Sozykin, Yandex.Money)

In Yandex.Money, we have been building microservice architecture for six years - we split up monoliths into small services and implement new functionalities as separate components.

Three years ago, we had seven proprietary platforms — four for Java and three for the JavaScript stack. It was expensive and difficult to accompany all this, but there was no need to talk about automation. We are tired of this life and have created a single platform for Java services based on the Spring Boot stack.

Today we have only two platforms, and for them the development tools have written so many automation tools that the process of testing releases and putting them into production is completely automated. There are almost no holivars on pullrequests now, so you can quickly start developing in any of more than 60 components.

In the report, I will tell you how we improved the testing process, covered most of the components with tests at least 80% and how we managed to achieve all of this.

And we here with the guys from the frontend argued whether java-developers are offended, if you call them javistami. The guys say it’s okay, but I doubt it, even though it’s not a javist itself.