Migrating from Imperative to Reactive in the Cloud

-- This is a free event --

Foojay.io (https://foojay.io) is the new Java community platform with everything you need to do your daily Java development work — with reference materials on the latest OpenJDK versions, vendors, and distributions, together with insights into the latest quarterly updates, articles, blogs, tips and tricks, and much more. And all for free, accompanied by a Slack channel for discussion on all things Java and OpenJDK.

To celebrate and introduce Foojay.io, members of the Foojay community are doing a JUG tour and one of the stops is right here. Come join in, learn about Foojay, and hear Nicolas Fränkel speak on Migrating from Imperative to Reactive in the Cloud.

Follow on Twitter - @foojayio (https://twitter.com/foojayio)

Abstract:
While Reactive Programming is very different from the usual Imperative way, there’s no denying it fits “the Cloud”, as every bit of resource is used to its fullest. Let’s see how to migrate from the latter to the former using a Spring Boot web app as an example. In this demo-based talk, I’ll show how to migrate a traditional Spring Boot application that uses WebMVC, Spring Data JPA, and Spring Cache to its Reactive equivalent in a step-by-step process.

About Speaker: Nicolas Fränkel
Nicolas is a Developer Advocate with 15+ years of experience consulting for many different customers, in a wide range of contexts (such as telecoms, banking, insurances, large retail and public sector). Usually working on Java/Java EE and Spring technologies, but with focused interests like Rich Internet Applications, Testing, CI/CD and DevOps. Currently working for Hazelcast (https://hazelcast.org). He also double as a trainer and triples as a book author.

Gentle Reminder:
We request all to follow general meeting etiquette in the meeting. Respect individual and personal views

Come to the meetings on time. We are ok with 15 minutes deviation. However any further delays will make the meeting irrelevant for you and un-necessary distraction for the speaker and the audience.

If you change your mind after RSVPing on the meetup please un RSVP. It helps in keeping track of the head count. We don't always get a bigger venue and its a last minute hassle to accommodate everyone in the meeting.