Depends on the use-case, but if your product is <14 month lifecycle App/shovel-ware, than go JS for the labor compatibility... Yet if you are hitting >40k concurrent users, the options winnow down fairly quickly.
The OTP offers a flat/simple architecture, and most people are puzzled the first time they see a Phoenix channels demonstration.
I think it is hilarious people assume 3NF or 4NF db schema can save them from bad design. Yet, many have tried to make SQL scale efficiently (with some obvious caveats) =3
https://quasar.dev/introduction-to-quasar/
That being said, Erlang/Elixir abstracts most db use-cases with ecto, and has some other incredibly powerful scalable features for sites:
https://www.phoenixframework.org/
* Distributed
* Fault-tolerant
* Highly available
* Hot swapping
Depends on the use-case, but if your product is <14 month lifecycle App/shovel-ware, than go JS for the labor compatibility... Yet if you are hitting >40k concurrent users, the options winnow down fairly quickly.
Have fun =3