Reactive systems. Munich 8 o'clock

This morning, we will discuss reactive systems. Systems that respond in real time, adapt under pressure, and survive failure — but what actually makes something reactive? Is it just async code and message queues, or is it a mindset? How do you balance responsiveness with complexity?

Come and share how you design reactive systems at your company. Which tools, patterns, or languages do you use — or wish you could? How do you test them, and what surprises have they thrown at you? Ask about it, tell about it, or listen about it, sipping your coffee.

Time: 08:00 (yes, early — but we start before the day steals your focus). Small group, every person matters. Can’t make it? Please update your RSVP.

Language: English

Format: One topic, a bunch of friendly people, open discussion. There’s no speaker. There might be prepared questions for the round, but the discussion may derail — and that’s fine. Whatever happens is the only thing that could have happened.

Entry level: None. Join if you’ve never built a reactive system but want to learn, or if you’ve been building them for years and want to defend or challenge best practices.