News for hackers. Stuff that matters.

A comment on Rails 5.0: Action Cable, API mode, and more. Parent comment

Re:Rails 5.0: Action Cable, API mode, and more by rozap on Thursday June 30, 2016 @06:48PM (#12012455)
I think most folks are finding that distribution in an erlang based application is a lot simpler, because you don't need to pull in things like redis for pubsub, memcached for caching, etc etc. erlang solves a bunch of problems in a rather elegant way that are solved in the java/python/ruby world through gobs of duct tape.
[ Parent | on HN ]
Re:Rails 5.0: Action Cable, API mode, and more by davidw on Thursday June 30, 2016 @06:51PM (#12012475)
Good point, but I'd see the actual codebase on a single node as the most important thing for most people. Even with Rails you can do a lot with one server.
[ Parent | on HN ]
Re:Rails 5.0: Action Cable, API mode, and more by Scarbutt on Thursday June 30, 2016 @07:02PM (#12012538)
Performance wise, I wouldn't put Java next to ruby and python, in what workload would the erlang vm beat the jvm?
[ Parent | on HN ]
Re:Rails 5.0: Action Cable, API mode, and more by felixgallo on Thursday June 30, 2016 @07:15PM (#12012623)
low jitter, low latency, high concurrency workloads.
[ Parent | on HN ]
Re:Rails 5.0: Action Cable, API mode, and more by rozap on Thursday June 30, 2016 @07:06PM (#12012563)
I'm talking more about concurrency and distribution models, not raw performance.
[ Parent | on HN ]