It depends on your goals for the backend. If you want distributed and fault tolerant systems, Elixir/Erlang is proven in that space for the last 30 years - as they both run on the BEAM. (I'm livin' the dream. I have the BEAM).
There are others that can explain this much better than myself, but the most fault tolerant systems don't come from a family of typed languages. Erlang with it's dynamic typing, pattern matching and OTP has been providing 99.99999% uptime for over 20 years. And, if you understand the trend in hardware CPU's with more cores and lower clock speeds, you certainly want to explore the BEAM as a tool to utilize those cores in an efficient and simple manner. Jim On Sat, Sep 10, 2016 at 11:09 AM, Dave Rapin <[email protected]> wrote: > Elixir is compiled to bytecode similar to how a JVM language like Closure > or Scala is. So not quite like C but similar to Elm. > > Also I assume you're taking about dynamic types which it has unlike Elm's > type system. I've heard however that Elixir's safer than your usual dynamic > language due to pattern matching. > > Depending on your use case I would alsoseriously consider a DBAAS option > like Firebase if your not much for devops or simply don't feel like > managing infrastructure. Combined with something like AWS lambda or > Google's cloud functions for a microsrrvice architecture (only when you > need it) it's pretty close to feature parity with a Phoenix type setup with > less effort. > > -- > You received this message because you are subscribed to the Google Groups > "Elm Discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Dr. Jim Freeze, Ph.D. (m) 512 949 9683 -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
