CIRCLE WITH A DOT

@nicd@masto.ahlcode.fi thanks for your answer! I guess I was picturing Erlang/Elixir web servers as being stateless, in that they would do all persistence with the relational database, at least for the lightweight processes that handle routing and HTTP request/response. What sort of processes would be alive for a long time for which would contain state that could make hot code reloading difficult?

Started to get back into Erlang yesterday, to to build a little something with MQTT. I had fun, but making stuff OTP-compatible was tough for me. The docs are there, but they are *dense*. Still wrapping my head around a lot of things.What are good resources for learning how to build IoT-adjacent services with Erlang/OTP?I mainly feed of Learn You Some Erlang for Great Good (https://learnyousomeerlang.com/), The Erlang Programming Language by Joe himself, and the recently discovered Let Erlang Crash (https://cloudstreet-dev.github.io/Let-Erlang-Crash/), as well as the reference documentation on https://erlang.org/docs/.#Erlang