Oftentimes, we see workflow driven applications as a series of long running processes that just wait. Sometimes we see threads being put to sleep and awoken after several minutes to see if things have changed. Usually, in these situations, we end up being dependent on the order of items in our system and we end up spending much of our time programming for the situations where these items occur “out of order”. Event-driven systems take a lot of that “out of order” complexity away and treat events happening in our system as always “being in order” and our application ends up managing the overall state. In this talk, we’ll look at the pros and cons to this approach to system architecture and design and how we can build a simple event driven system using a messaging framework/toolset like, but not only, Akka.NET.
David Hoerster, a 5-time C# MVP, is a recovering corporate financial analyst and has been working with the Microsoft.NET Framework since the early 1.0 betas. He is the Sr. Solutions Architect for Confluence, a managed investments software product company. David is the conference chair of Pittsburgh TechFest, the leader of the Pittsburgh Reactive Systems user group (http://meetup.com/reactive), the former president of the Pittsburgh .NET User’s Group (PGHDOTNET) and is also a regular speaker at Pittsburgh and regional user group and community conference events. David can be found rarely blogging at http://blog.agileways.com and tweets occasionally at @DavidHoerster.