News for hackers. Stuff that matters.
Re:Why we used Pony to write Wallaroo by spooneybarger on Thursday October 26, 2017 @12:45PM (#15560580)
I want to preface this with: I love erlang. We use Elixir for the service that powers metrics display for Wallaroo. When I learned Erlang several years ago, it made me a better programmer.

At the time we made the decision, we were worried about Erlang being able to meet the latency and throughput goals we had. I knew a number of people who worked on Riak at Basho and had a few lengthy discussions about Erlang performance. They felt that we could end up struggling to get the performance we were looking for.

I had never used Erlang for any large scale project and deferred to their wisdom and knowledge.

As it turns out, the approach that we've used to support languages like Python is in process, using C to bind Wallaroo with the other language. This probably would have been more difficult with Erlang as well, but that's hindsight.

Erlang is an awesome language. It has an amazing VM. That we didn't think it was right for us should in no way discourage anyone else from using it.

Re:Why we used Pony to write Wallaroo by fasquoika on Thursday October 26, 2017 @01:22PM (#15561012)
Is your application CPU bound? Because that's generally where Erlang's performance is lacking. I'm pretty sure you wouldn't run into performance issues in Erlang if you're doing an IO bound task
Re:Why we used Pony to write Wallaroo by spooneybarger on Thursday October 26, 2017 @01:29PM (#15561097)
Wallaroo is a framework for end users writing applications. It is not an application itself. Many of the use cases that people come to us with are very CPU intensive.
Re:Why we used Pony to write Wallaroo by fasquoika on Thursday October 26, 2017 @04:00PM (#15562462)
Thanks, that makes sense