How And Why We Switched from Erlang to Python (2011)

nemothekid wrote: post #3

1. This article was written in 2011 (it's 8 years old). I was confused why they were going with eventlet, but the age of the article explains why. 2. Even for 2011, 1k rps with an average latency of 100ms seems laughably bad. I have to be missing something here.

> No one on our team is an Erlang expert

Perhaps that has something to do with it

Re: How And Why We Switched from Erlang to Python (2011)

#7

Post by 59nadir » Sun, Apr 28, 2019, 5:41 PM UTC

If you're able to make a faster service handling many concurrent requests in Python, you indeed should've never used Erlang from the beginning, because you clearly didn't know at all what you were doing. This article is spot on in that regard.

Re: How And Why We Switched from Erlang to Python (2011)

#8

Post by pdimitar » Sun, Apr 28, 2019, 5:42 PM UTC

Them not being able to utilize Erlang well seems to be the gist of the article. The rest seems like a post-hoc rationalization.

It's fair to switch away from a technology your team doesn't know well and doesn't want to learn. Maybe that should have been the title.

Re: How And Why We Switched from Erlang to Python (2011)

#9

Post by sk5t » Sun, Apr 28, 2019, 5:43 PM UTC

Gee whiz, you mean it's a good idea to choose a language/framework one knows well for implementing production services? Or maybe bring in an Erlang expert as a consultant to fix things?

Re: How And Why We Switched from Erlang to Python (2011)

#10

Post by giancarlostoro » Sun, Apr 28, 2019, 5:43 PM UTC

Sometimes using the right tool for the right job also means making sure you have people who can use said tool.