@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?
