Hello Kotlin enthusiasts!
Join us on an evening filled with enticing food, refreshing drinks, and insightful Kotlin discussions.
Make sure to press the RSVP button!
Wibautstraat 200 — 202, Amsterdam
18:00 — Doors open, food and drinks 🍕
18:30 — Opening 🎙️
18:35 — Unraveling the most Kotlin-Friendly Framework: Springboot vs. Quarkus vs. Micronaut. Who Claims the Krown? — Urs Peter 💻
19:30 — Small break and drinks 🍻
19.30 — Beyond K2: What features are next and how you can use them — René Bulsing 💻
20:00 — Safe concurrency: resources and resilience — Alejandro Serrano Mena 💻
20:45 — Chats & Drinks 👥
Unraveling the most Kotlin-Friendly Framework: Springboot vs. Quarkus vs. Micronaut. Who Claims the Krown?
Urs Peter — Software Engineer @ Xebia Software Development
Kotlin without a framework won’t get you far. So, which is the best choice out of the most popular server-side frameworks for the JVM out there?
In this talk, I will put the big three in the arena to see which will emerge as the undisputed winner of the most Kotlin-friendly framework. Along the battle, we will explore various Kotlin-specific additions like serialization support, custom DSLs, Kotlin extensions, and — last and not least — Coroutine support, which helps tame the overly complex reactive flavors the different frameworks offer.
Join us for a contest between Spring Boot, Quarkus, and Micronaut as they compete for the Krown while enjoying a parade of exciting Kotlin features and distinguishing capabilities each framework proposes.
Beyond K2: What features are next and how you can use them
René Bulsing — Software Engineer @ Xebia Software Development
The upcoming release of K2 and Kotlin 2.0 will not include many new features right off the bat, but soon after, we can expect to see some exciting new releases! Let’s explore a number of these new features and use some practical examples to show why they’re so exciting.
Safe concurrency: resources and resilience
Alejandro Serrano Mena — Software Engineer @ Xebia Functional
Modern applications, in the front- or the back-end, usually require the collaboration of many different services to fulfill their tasks. This brings two important problems to the table: how to manage the resources required to access those services and how to protect the application from transient failures. This complexity becomes even bigger when concurrency enters the game.
In this talk, we discuss the tools provided by the Arrow project to better handle these scenarios (but no previous experience with Arrow is required). Resource scopes and SuspendApp provide management of resources at a local and application level. The resilience library exposes well-known patterns like circuit breakers and retry schedules. Sagas allow for distributed transactions to succeed of fail as a unit.