Representing IoT Systems with the Actor Model and Akka.NET 1
There will be over 20 billion connected things in use by 2020. This course will teach you why the Actor Model and Akka.NET is a good fit for representing IoT systems that support reactive, concurrent, scalable, distributed, and fault tolerant apps.
What you'll learn
Traditional programming techniques can fall short when trying to represent IoT devices and systems due to the the need for concurrency management, scalability, reactivity, distribution, and fault tolerance. In this course, Representing IoT Systems with the Actor Model and Akka.NET 1, you will learn how to model Internet of Things devices as actors with Akka.NET. First, you will learn why the Actor Model and Akka.NET is a good fit for IoT systems. Next, you will explore how to model devices as actors and organize actors into groups and supervision hierarchies. Finally, you will discover how to model the querying of device actors as separate actor instances. By the end of this course, you will know how to design and implement actors that represent real-world connected devices in IoT scenarios and take advantage of the built-in features of Akka.NET such as concurrency management and fault tolerance.
Table of contents
- Introduction 1m
- Design Overview 2m
- The Request-response Pattern 2m
- Adding a New TemperatureSensor Actor and Test Class 2m
- Testing Actor Initialization 6m
- Testing the TemperatureSensor Starts with No Temperature Reading 3m
- Updating the Temperature Reading 3m
- Testing Sensor Registration 4m
- Testing Unhandled Message Behaviour 3m
- Summary 1m
- Introduction 1m
- Design Overview 1m
- Adding a New Floor Actor and Test Class 1m
- Registering New TemperatureSensor Instances 6m
- Returning Existing TemperatureSensor Instances 4m
- Only Registering New TemperatureSensors for Correct Floor 3m
- Listing All AllTemperatureSensors IDs 3m
- Monitoring Terminated TemperatureSensor Child Actors 4m
- Summary 1m
- Introduction 1m
- Design Overview 1m
- Immutability of Messages 2m
- Implementing Message Immutability 3m
- Adding a New FloorsManager Actor and Test Class 1m
- Adding New Message Classes 1m
- Listing Floor IDs 2m
- Registering New Floor Actors 2m
- Reusing Existing Floor Actors 1m
- Monitoring Child Actors for Terminated Messages 4m
- Summary 1m
- Introduction 1m
- Design Overview 5m
- Adding a New FloorQuery Actor and Test Class 1m
- Adding Temperature Result Classes 2m
- Adding New Message Classes 2m
- Adding an Initial Test 6m
- Querying Temperature Sensors 5m
- Returning Results When No Temperature Reading Available 2m
- Handling Sensors That Stop During Query Execution 2m
- Dealing with Sensor Timeouts 4m
- Initiating a Query from the Floor Actor 4m
- Summary 1m
About the author
With over 15 years of experience in both frontend and backend software development, Jason Roberts is a freelance developer, trainer, and author. He holds a Bachelor of Science degree in computing, is the author of several books, and writes at his blog DontCodeTired.com. Jason is an open source contributor and in addition to enterprise software development, he has designed and developed Windows Store and Windows Phone apps.