In days

21-24 March 2022

Online, GMT+2
14:00 - 15:00
Automation is key these days, to save time and avoid mistakes. Bicep is a new Domain Specific Language (DSL) that drastically simplifies the way of writing Infrastructure as Code for the Azure platform. In this session we'll go over this new language and learn how to get started. We'll then look at how you can automate the deployment of your infrastructure as code using Octopus Deploy's Runbook capabilities.
15:00 - 16:00
You can’t develop a device any more without it connecting to something. These ‘smart’ devices all have one thing in common: they generate a never-ending stream of data. If you want to process all that data for 100, 1000 or 10000 devices, you can probably get by with a very simple web stack. But as soon as you want to scale to 1000000 or more devices, you’re going to need a better strategy. Scaling software is always tricky. We all have been through this. You load balance your web farm only to find out that your database is a bottleneck. Or to find out you need to synchronize caches across your farm, etc. Akka.NET and its implementation of the actor model make scaling a bit easier. Developing stateful code becomes a breeze, as well as scaling it and making it resilient. But there are pitfalls as well. No prior Akka.NET knowledge is required.
16:00 - 17:00

Learn about new features delivered in C# 10 that will make you more productive: Even more patterns, and record structs are major changes. Other smaller changes will make you just as productive. As time permits, we’ll take a look at some of the ideas for C# 11. Potential features include list patterns, !! for null parameter checking, and more string improvements.

17:00 - 18:00
Domain-Driven Design is a vast topic. There are so many wonderful concepts, philosophies, patterns, practices and techniques to learn and benefit from. Some of the best minds in the industry have been tuning these practices for years to ensure developers are able to implement proven, successful approaches to software design. Domain modeling in particular is very specific with guidance on designing and coordinating the dance between the myriad moving parts in our system. Yet learning the principals of DDD can be daunting for developers who are new to DDD. To encourage and enable more developers to get on the path of DDD, is it reasonable to allow a more pragmatic approach over a principled approach of adhering strictly to DDD guidelines? Should developers be encouraged to start with low hanging fruit which they can quickly benefit from in their software projects while they continue to learn, to gain a deeper understanding of Domain-Driven Design in order to evolve and adapt their practices as they move closer and closer to the beauty we all know that can be achieved with DDD.

Workshops

Get in touch

Iași, Romania
info@dotnetdays.ro