Reactive Applications with Akka.NET

Chapter 3. Your first Akka.NET application

This chapter covers

• Setting up an actor system
• Defining an actor
• Sending a message to an actor
• Evaluating alternative actor implementations

The first few chapters covered what reactive architecture means, as well as the key reasons you’ll likely want to use it. You’ve seen how the aim of a reactive system is to create applications that are responsive to the end user, and how this requires applications to work, even when struggling with the demands of scale or malfunctioning components. We’ve also covered the key things you need to consider when designing a reactive application.

For the rest of the book, we’ll consider how you can write reactive systems that follow the principles ...