We host quarterly meetups for .NET developers and Microsoft Azure enthousiasts. Join us in-person in Nieuwegein, The Netherlands. We do not host online sessions and we do not post sessions online after the event.
Welcome to DotnetFriday, the ultimate meetup platform for .NET developers and Microsoft Azure enthusiasts in the beautiful Netherlands! At DotnetFriday, we combine valuable knowledge sessions with a fun and vibrant community. Whether you’re a seasoned developer or just starting out, our engaging talks led by industry experts and Microsoft MVPs will sharpen your skills and keep you up-to-date with the latest .NET frameworks and Azure developments.
But it’s not all serious learning - we also provide a lively atmosphere for socializing, networking, and making lasting connections with like-minded professionals. Join us at DotnetFriday and embark on a journey of continuous learning, personal growth, and unforgettable experiences in the world of .NET and Azure development. See you at our next meetup!
Here some of the topics we have covered the past sessions:DotnetFriday events always start at 16:30 CEST. We allow attendees to arrive and settle with a drink for about half an hour. The first session typically starts at 17:00 CEST. A usual DotnetFriday evening looks like so:
| Start (CEST) | End (CEST) | |
|---|---|---|
| 16:30 | 17:00 | Walk in, take a drink and have a chat |
| 17:00 | 18:00 | First session of the evening |
| 18:00 | 19:00 | Food, drinks & networking |
| 19:00 | 19:20 | Lightning talk (this timeslot is optional does not always take place) |
| 19:30 | 20:30 | Second session of the evening (might start 30 minutes earlier in case of no lightning talk) |
| 20:30 | 23:00 | Drinks and bites, having a chat and a laugh |
We strive to make DotnetFriday as fun as possible. We invite you to stay for a drink and have a laugh after the last session finished, although we do understand those who leave and enjoy their evening elsewhere. Please note that we may deviate from the standard program here and there, each and every DotnetFriday edition is unique ;)
Full-stack software engineer at 4Dotnet, specialized in .NET and Azure. I like to work with event-driven systems and microservices, but also know my way around frontends, specifically Angular, React and Vue.
Dapr promises portable distributed application building blocks. Aspire promises a streamlined local developer experience for cloud-native applications. Combined, they form a powerful platform for building observable, event-driven microservices without drowning in infrastructure complexity.
In this session, we’ll start with a quick introduction to Aspire and set up a distributed application from scratch. From there, we’ll explore the core Dapr concepts: the sidecar architecture, building blocks, and components. You’ll see how Aspire makes it easy to enable Dapr on services and orchestrate everything locally with minimal setup.
Using practical demos, we’ll walk through Dapr Pub/Sub messaging, state management with a state store, and service observability using OpenTelemetry. Along the way, we’ll discuss how these patterns help teams build resilient, maintainable distributed systems while keeping developers productive.
By the end of the session, you’ll understand how Aspire and Dapr complement each other, how to get started quickly, and how to apply these patterns in real-world .NET applications.
Dennis van der Stelt is a software architect with a strong focus on distributed systems, messaging, and resilient software design. With deep expertise in .NET and C#, he helps teams build scalable, maintainable systems using patterns like event-driven architecture, CQRS, and vertical slices. Dennis regularly speaks at conferences, writes technical blog posts, and isn’t afraid to challenge conventional wisdom—especially when it’s wrapped in hype. Known for combining sharp insights with a dose of dry humor (and the occasional pop culture reference), Dennis makes complex topics both practical and engaging.
How often did you see a session about any kind of services and heard about how important it was to find the right boundaries, but until now you wondered how to find those boundaries. Or what vertical slices look like once implemented, how they behave and what data they own. And how on earth business data cannot cross its boundaries, but invoices need access to product, customer, and pricing details.
In this session, we’ll see an example of how the planet’s largest electronic retailer would find the service boundaries for its checkout process. Then we’ll look at how each service is part of choreographing this complex business process in an actual implementation. You’ll finally understand the full flow from finding service boundaries to implementation and be able to break down a big ball of mud into a maintainable and decoupled system.
