Micronaut vs Spring Boot, or who's the smallest here?

Day 2 /  / Track 1  /  RU

You are doing enterprise development and working with slow app servers? Every day you implement all of the EJB 2.0 interfaces and pack them into OSGI bundle? Your friends tell you about new lightweight frameworks, but you don't have time to try them?

We'll help you decide whether you should go out to the brave new world (but we still don't know that for sure) or stay in your cozy little warm nest, encrusted with moss. Together with you we'll try to find the standard to define how "micro" a framework is (if such standard does actually exist). Of course, we'll start with Spring Boot. Malicious gossip has it that Spring Boot could lose some weight, but we know what to say to those fat microservices! And, to make it more exciting, we found an opponent for the already not-so-hipster SB2 — Micronaut. Though maybe there is someone small enough in Spring Boot's own family.

In practice, developing and testing, testing and developing, we'll see the compromises in developing on SB2 and Micronaut. We shall see who's the best of the best: the most reactive, the handiest, the "cloudiest" — and is "micro" even good for production?

Download presentation
Kirill Tolkachev

Up until recently Kirill was a lead developer at Alfa-Lab. He was developing different banking APIs, forming principles and tools related to microservice architecture. He is a fan of Groovy, Gradle, Spring and Netflix technologies stack. Kirill is a resident of famous Russian IT-podcast "Razbor Poletov". He knows DevOps methodology like the palm of his hand and has four years' experience of its production usage.

Maxim Gorelikov

Maxim is working on API development for mobile apps and security layers. Basically, he uses Spring and Netflix ecosystem, but checks out everything that is worth trying on GitHub.

He is experimenting with reactive approaches, a couple of experiments got to the production level.

He wants to understand not only his apps but also everything around them, thus he is working with all the infrastructure (logs, CI/CD, orchestration). To sum up, DevOps is our everything.

Speaker's previous talks