| Something I often "draw" to other developers when showing Elixir is the difference in terms of "boundaries". It is common to have: frontend <-JSON-> backend <-db/queue-> background jobs Each boundary introduces complexity (marshalling / impedance mismatch / but also different HR/recruiting needs). In Elixir you can more or less do: front/back/background with no boundaries or reduced boundaries (e.g. using LiveView & OBAN in the same process, even if going through Postgres as a queue). Someone coined the term "deepstack engineer" as well recently I think, which I could draw as: frontend <-> backend <-> background <-> machine learning Now with Elixir you can do everything in the same process (but with isolation as required): front/back/background/ml And this is something I find really interesting about this stack. |