Building an IoT Demand Response solution with Elixir
summary
Prototype converts an RFP into an Elixir system that models each physical device as a GenServer, uses a durable message store and Influx for time‑series, parses binary device protocols with ~600 lines of code, and load tests with Gatling and AWS mocks. Property‑based tests validate state and time‑series integrity. Proof‑of‑concept handles 100k chatty devices by extrapolation after running 40k on one server and demonstrating stateful GenServer + durable message store behavior, but disk hotspots and stateless cloud constraints complicate production adoption.
AI-written summary · about
chapters (17)
- 0:00Intro
- 2:55Power grid
- 3:35Demands
- 5:04Frequency
- 5:18Demand Response
- 5:55Blackouts
- 6:06What did the customer win
- 6:37What is the business domain
- 7:25How would you model this
- 8:35IOT Platform
- 13:02Gatling
- 13:40How many servers
- 15:26Did they buy
- 16:38Stateless
- 17:07Race Conditions
- 18:14Scaling
- 19:29Outro
related talks
40mThe Benefits of Tierless Elixir/Potato for Engineering IoT Systems
49mConnecting the Internet of Things
49mDesign patterns for distributed client server systems via IoT
41mKeynote Panel discussion: Erlang all the things
36mConnected Device Development by Contract
43mAn Approach For The Internet Of Things
50mScaling IoT
43mIndustrial IoT in practice