2 ms·
> Immediate wins [...] We were able to get rid of some servers, and downsize the remaining servers [...] Response times are down as well [...] Development and d
by rdtsc 10y ago
> 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.
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.
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.
- themartorana 10y agoOps wins should just be assumed, though. Not to be flip, but you'll gain performance wins picking just about any other language/stack than Ruby on Rails. Even Python blows it out of the water. Move to something like Erlang/Elixir with a ridiculously nice/tuned runtime, or compiled languages like Go, or a combination of the two like Java/.NET and you should see huge performance wins without much work. Rails wins in some cases for development productivity, and is "good enough" for many things. But when it's time for scaling, the language/solution/stack choice almost doesn't matter if you're moving from RoR. That said, if free ops performance wins aren't part of the decision, you've done it wrong.
- rdtsc 10y ago> Ops wins should just be assumed, though They should be, but often they are not I. It is mostly about "Look how fast it runs on my laptop, it means we can have millions of requests on a large server". I've heard people quote Techempower benchmarks as their reason to picking a language / library vs another.