> Immediate wins [...] We were able to get rid of some servers, and downsize the remaining servers [...] Response times are down as well [...] Development and deployment are also faster.<p>A case for new technology should be made more than just on pure technical features but also in terms of reduced ops load, say because of fault tolerance or saving in recurring infrastructure costs. Or it could be community friendliness and acceptance of new members. I feel Elixir does a great job there, as well.<p>Other thing I found using Erlang: It is simply more fun and easier to discover problems. Can launch observer. Setup traces with recon_trace (I started to do that more lately even instead of adding print statement to code, attaching traces to functions is just too easy). Even things like hot-patching have saved the day many time in terms of fixing an issue for some customers with 0-downtime. These seems like nice extras but they all add up and make a huge difference when taken together.
I started using Phoenix for my most recent side project. So far, am really liking Elixir and everything that comes with it. Obviously, I am still learning, but the inclusion of the entire Erlang ecosystem is a big plus.<p>Will have to say that working with Elixir and Phoenix (so far) has been much more enjoyable than working with Rails.<p>I will say the only thing I really miss is extra tooling for debugging and so on, but I'm primarily a java developer, so I'm used to having all sorts of options at my fingertips for debugging.
Great news, more people discover how good Erlang(and obviously Elixir) is, especially comparing to Ruby/Rails. I hope more people are going to consider it.
A few weeks ago I wrote a very basic IRC server in Elixir to learn the language and was very impressed how fast I was able to get it running. Despite it being my first contact with a functional language the coding felt very intuitive to me.<p>The only thing I miss is good tooling support but I'm coming from Java and a bit spoiled in that regard.
"Elixir is blazing fast" it says, so I follow the link and notice that "blazing fast" apparently means 10x the speed of Ruby. I don't think that phrase means what they think it means.
Just a note for blog authors - please add link to your product on your blog, in visible. I almost didn't check what you do, because I'm almost too lazy to click on address bar and remove "blog" prefix.
We've being playing with Elixir and are planing to ship first production app in the Fall. Very productive and unique environment. Coming from node it's so much nicer for concurrency not to mention all the other cool features of BEAM VM.
Can someone explain this? "Umbrella projects ... [are] a really great concept that allows us to have multiple microservices living in the same codebase, while giving us the flexibility to scale each service separately". How is this any different from just storing the code for multiple services in the same repository?