I know these are a lot of questions, all at once. But in a way, they are all the same question:
How do you typically use Erlang in internet facing applications?
And it’s clearly a loaded question as once something is internet facing, there’s a whole boatload of security concerns, which may or may not dictate a bunch of architectural concerns, which impacts how you compose things, and this impacts how you deploy the things.
Fixed link: How do you deploy Erlang applications in cloud?
For personal context: I’ve been wishing I could use Erlang at my various jobs for the past 15+ years, but have been more or less stuck with java, go, python, etc., and in the process, re-inventing erlang, but poorly (iirc either Armstrong or Virding was quoted as saying something like, “any reasonably complex software endeavor will re-invent 80% of erlang/otp, but poorly”). Anyway, with the advent of Gleam, I think I can make a stronger pitch that this is the way to go. But first, I need to understand some of these architectural concepts first. I really don’t want to be the guy that deploys a system that get’s pawned b/c I didn’t understand some core concepts and security constraints that everyone who’s steeped in this already knows.