From Monolith to Microservices & Concurrency models explained

Skyworkz Utrecht
Skyworkz Utrecht
Public group

Tractieweg 41

Tractieweg 41 · Utrecht

How to find us

We are in the big building called Werkspoorkathedraal - on the backside. Use Nijverheidsweg 20-18, Utrecht for Google Maps for approaching the building from the correct side. We are in Studio-B.

Location image of event venue



18:00 - Food 🍕 & drinks 🍺
19:00 - Changing architecture in production while also migrating to the cloud
20:15 - Three concurrency models that every developer should know about
21:15 - Socializing with drinks 🍻 🍷 🥤


TALK #1 - Changing architecture in production while also migrating to the cloud

When your application is around long enough making changes to the core architecture is going to be inevitable. A complete rewrite of the application might sound tempting, but often isn't financially viable and might not actually solve the issue. The answer is to evolve your application's architecture.

But how do you do this when your application is in production and you need to keep delivering value for the business? In this talk, Sven Rienstra is going to explore this subject using a case study. He'll show he migrated from a monolith to a microservices architecture and how the application was moved to the cloud simultaneously.

TALK #2 - Three concurrency models that every cloud developer should know about.

Concurrency is everywhere. All systems depend on concurrency. Many languages have built-in concurrency primitives, and we're used to using those. However, we are often looking for the best tool for the job. What if there's another concurrency model that fits better in a particular project?

In this talk, presented by Mikhail Vaysman, we look at 3 models: Threads and Locks, Communicating Sequential Processes and Actors. I'll talk about each model and show you how you can write the same example using a particular model.