I should note, this isn't my proposal. Just found it interesting enough to share
227 karma · joined October 15, 2013
I'd suggest looking at Elixir/Phoenix if you have a problem with Rails that you think Elixir/Phoenix might be able to solve. Could be scale problems, reliability, real-time communication, etc.
I wouldn't suggest replacing your entire Rails app with Phoenix right away. If possible start with a service that may be having issues and migrate that over if possible.
As with everything though, there are trade-offs. If going strictly AWS fits your use case, you're fine working with GraphQL, etc., go for it.
The channels abstraction was the driving force behind our choice and at the time there wasn’t anything that stood out in the Java world.
What we did do from scratch was write the instrumenting of Wallaroo in order to collect the metrics that could be used by our Metrics UI or Prometheus.
We thought it'd create a better user experience to provide a tool that provides the metrics information in a meaningful way as opposed to letting our users pick from Prometheus, Grafana, etc off the bat and having them set it up themselves.
In the end, if a user wants to use a tool like Prometheus they can write an adapter to convert our Metrics Protocol into a format suitable for Prometheus.
We have a few clients who will be running Wallaroo in production in the upcoming months. We're still a fairly new product, hoping to have one of those stories out in the not so distant future.
Is there anything you'd like to gain from one of those stories? Would be helpful to us to have a target audience in mind.