Re:Wallaroo: a fast, scalable data processing engine
by buttershakes on Wednesday September 27, 2017 @08:04PM
(#15353457)
This is so cool. I see you used Erlang for various components like the UI, was your primary reason for using Pony instead of Erlang for the data processing performance? That seems like a safe assumption given Erlang's frustrating performance characteristics. There isn't a lot of information out there about Pony vs Erlang in production, hopefully you guys will write up more in the future about the differences you have encountered.
[ Parent
| on HN ]
Re:Wallaroo: a fast, scalable data processing engine
by spooneybarger on Wednesday September 27, 2017 @08:10PM
(#15353479)
Thank you for your kind words. It's nerve wracking when you finally pull the trigger and say "we need to get this out there".
Re: Pony vs Erlang.
Point 1: we love erlang.
There's a short version of the answer to your question starting around minute 49 of my QCon NY talk: https://www.infoq.com/presentations/pony-wallaroo
And yes, I am planning on writing more about why we went with Pony (which led to my becoming a member of the Pony core team).