I should note, this isn't my proposal. Just found it interesting enough to share

Thanks for sharing.

Not really a question that can be answered.

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.

Most likely, yes.

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.

Truthfully I don’t have many thoughts on that combination.

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.

Sometimes I get upset that my favorite pizza spots in NYC are cash only and non-delivery but after reading this I’m sure the quality wouldn’t be the same if they switched.

the Elixir community was very helpful in making this possible. Happy to give back in some fashion

Hi, I'm the author of this post. Would be happy to answer any questions if folks have some.

Very interesting post. Could you elaborate more (maybe another blog?) on the DevOps perspectives on how to manage a prod Elixir/BEAM stack (CI/CD, scaling, dev vs test vs prod environment management)?

If you have a decent engineering + ops background (which your comment indicates you might), we're hiring.

http://careers.wallaroolabs.com/apply/FjrSD7HjmW/DevOps-Engi...

Looking for a combination role that crosses what is often considered SysAdmin and what is considered SRE.

We don't run infrastructure ourselves but have clients who are starting to run Wallaroo in production and we are looking to hire someone who is focused on making sure the end developer lifecycle experience is awesome.

This would mean touching everything from installation of the Wallaroo development environment through documenting best practices for running in production to contributing to the core Pony and Elixir codebases in order to add new functionality.

Not sure if this totally answers your question, but gigalixir.com might be able to help you with CI/CD, scaling, and prod environment management. I'm the founder.

Hi, I'm the author of this post and I'll be happy to answer any questions here.

Thanks for the write-up. Why did you DIY instead of using an existing system like e.g. Prometheus?

We didn't set out to replace Prometheus, our Metrics UI was designed to give Wallaroo users insight into several parts of the system to spot bottlenecks while developing applications.

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.

I see, thanks!

Wallaroo seems like a well-thought-out system, but it’s hard to find any case studies or mentions of real-world enterprise/startup use of the product, and therefore it’s tough to justify trying it out. Are any of those stories coming down the pipeline as well?

Thanks for the encouraging comment, we've spent a lot of time on Wallaroo's design so we're happy to see people appreciate it.

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.

Hi, I’m the author of this blog post. If anyone has any questions I’ll be happy to answer.