Overview of the most interesting reports Joker 2018: version EastBanc Technologies
In this post, we want to share our impressions of the conference for Java-developers Joker, which we heard most of all we heard.
We hope this will help you navigate the video from the conference when they appear in the public domain. In the meantime, we added links to presentations wherever possible.
You can listen if you’re doing machine learning. Although it is not very clear for whom the report was intended. If people understand, then for them it is no longer interesting. If they do not understand, they will not understand the report, too little information is needed for understanding.
The main message is this: you can use google TensorFlow to train models from Java, but support for learning is limited. But you can use trained models. For example, load a trained model into TensorFlow-microservice and send it requests from Java or another microservice to get a response. For example, recognize the picture, tell by the symptoms, what kind of disease
And the TensorFlow team has Docker Image with TensorFlow, which can be used to upload models there and send requests for applications of these models. Sweet!
Micronaut vs Spring Boot, or Who is the smallest? - Kirill Tolkachev and Maxim Gorelikov
Cyril and Maxim compared modern frameworks in terms of launch speed, in terms of the amount of memory required for starting up, and in terms of coding complexity.
One fact caught our attention: Micronaut implements DI at compile time, and Spring implements at startup /work. This allows Micronaut to run faster. But until the release version of Micronaut came out, I have to take my word for it.
Vadim Tsesko talks about the architecture of the music distributor in Odnoklassniki. The report has a description of servers and their roles, a description of balancing and how Fault Tolerance and High Availability are ensured. Separately - about the reactive approach on a real case without any special technical details. OK showed a working example of using a reactive approach.
Various concepts, best practices and architecture for obtaining a fault-tolerant service due to balancing and replication and other data caching tricks for fast delivery of data to the user are presented. As always, in the presentation, OK has a bunch of links for more in-depth study of the topic from the slide.
Reactive Spring - Josh Long
The report we were driving for :) Actually, no, but Josh Long is one of two big stars of the conference. His report is cool, combines both humor and technology.
What we call a report in practice was this live coding session on creating reactive microservices using Spring WebFlux. It gives a general understanding of what the Reactive API is, offers an example of use in Spring ? and the bonus is a cheerful presentation of material. There was also an example with Reactive Proxy as an alternative to Zuul. We advise everyone to look.
The world has finally become reactive. Or the overall impression of the reports Joker
There were many reports about this and even more it was discussed in the discussion areas. In fact, the big question is whether the world has become reactive or whether it has been like this for a long time, but now they have come up with a new name for the old patterns and poured new blood into them.
Among the reports on reactivity were for every taste: and purely technical, for example, Josh Long, who told how to do reactivity in the spring. And real cases of reactivity - for example, Vadim Tsesko from Schoolmates.
Our main technology is Spring, so the Josh Long report is a must-see. (3r33279. The link to the repository from the report 3-333280.). There is an example of a reactive service that works with Mongo reactively and a reactive service that reactively proxies another reactive service. It was quite helpful for us to find out.
It may be interesting