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 ;)
Developer working with .NET and Azure.
Failure isn’t a matter of if, it’s a matter of when. You spend countless hours designing, planning, and building robust and resilient systems. Even with all that effort, it is impossible to prevent all failures.
When the inevitable happens at 3:00 AM, do you know how your self-healing architecture works as designed in production?
This is where Chaos Engineering comes in. With Chaos Engineering, inject real failures into production systems to validate that they behave as designed. Does this mean we just start turning off random things?
No, instead we take a scientific approach, where we create an experiment to test whether the system behaves as designed. When you start with Chaos Engineering, you are no longer just designing resilient systems and hoping that everything works when the inevitable failure happens.
Now when there is a failure at 3:00 AM, you are prepared and know how your production systems will behave.
With Chaos Engineering:
I’m developing software for over two decades. I’m working as a cloud solution architect and a team lead at 4DotNet in The Netherlands.
In my current position I love to help customers with their journey to the cloud. I like to create highly performant software and to help team members to a higher level of software development.
My focus is on the Microsoft development stack, mainly C# and the Microsoft Azure Cloud. I also have strong affinity with Angular.
Your app just went viral. Congrats. Now Sydney is complaining about lag, your database is sweating, and you have no idea what a “twin region” is. Let’s fix that, together.
This talk tells the story of an app that did everything right and got popular, and then had to grow up fast. We start where every success story quietly falls apart: one region, one database. First we pull back the curtain on how Azure’s global footprint actually works, regions, availability zones, and why the old “paired region” thing isn’t the safety net it used to be. Then we spread the app itself across the world and let Azure Front Door send every user to the closest happy instance, instead of making Sydney talk to a server in Amsterdam.
And then, the fun part. The data. Because two people on opposite sides of the planet are about to hit save at the exact same second, and something has to give. We’ll walk through the real options, one database per region, replicas that follow your users, and Cosmos DB’s “everyone can write, we’ll sort it out” approach, no sugarcoating, trade-offs included.
By the end you’ll know exactly what to do the next time success hits the fan, instead of finding out live, in production, at 2am.
