The Edge is the new frontier of computing possibilities, offering promises, opportunities, and it’s own set of challenges. In this talk, we’ll break down what it is, why it’s awesome, and how it fits into your application architecture.

We’ll cover things like: - What are the benefits - What are the limitations - When it makes sense - When it doesn’t make sense - How to get started

Objective

Attendees will consider the importance of architecture on the success of a product over time and be introduced to how Domain Driven Design interacts with clean architecture.

Keys

• Attendees thinking about architecture
• Share we've learned from reading Clean Architecture by Uncle Bob Martin in an Omnitech book club and presenting about the subject.
• Introduce Domain Driven Design (DDD) and new things I've learned since reading Clean Architecture at Omnitech through a series of lunches using Pluralsight and through Domain Modeling Made Functional: Tackle Software Complexity with Domain-Driven Design and F#: by Scott Wlaschin book.

Developers are bombarded with technical decisions every day. What language should I learn? What framework should I use? What software will make my life easier? The list goes on and on. A simple decision can have rippling effects in your organization, both good and bad. Technical decision making isn’t so much about which tool to pick, rather what problem to solve. In this presentation, we explore various approaches to technical decision making, including techniques for gathering and evaluating information, strategies for managing uncertainty and risk, and methods for involving and engaging team members. We also discuss best practices for evaluating the success and effectiveness of technical decisions. The aim is to provide a practical guide for technical leaders looking to improve their decision making skills and make more effective technical decisions.

During this workshop we will collaborate, design, and implement a solution that will result in a working, business-focused, event-driven application in modern C# (dotnet). If you want to be involved from building a solution from scratch this is your opportunity.

We will begin by Event Storming, which is a workshop-based method to quickly find out what is happening, or needs to happen, in the domain of our software application. This means of business-process modeling and requirements engineering will enable us to begin designing our application. Our application will instill Domain-Driven Design concepts so we can bake business logic into our code to be expressive, understandable, and maintainable. We will also utilize CQRS and Event Sourcing to capture state changes and intent, allowing us to make an application that is robust, performance-minded, and observable.

We will discuss how these strategies can reduce business complexity, make our applications far easier to maintain and evolve, and going over the open source software that can make it happen.

If you want to see "real world" development that is focused on the domain and how that translates into powerful, modern, asynchronous software then this is a workshop you do not want to miss.

Note: A code repository will be publicly available to provide a helping hand in interest of time and comprehension so no one is left behind. This course assumes you some knowledge in C#, SQL, and Docker. Working experience in a language comperable to C# like Java could certainly follow along.