3 ms·
There are tons of blog posts about companies that have switched from Ruby or Python to Go and have been able to massively scale down their amount of servers whi
by insertnickname 10y ago
There are tons of blog posts about companies that have switched from Ruby or Python to Go and have been able to massively scale down their amount of servers while handling the same load. Here's one example: https://www.iron.io/how-we-went-from-30-servers-to-2-go/ https://www.iron.io/how-we-went-from-30-servers-to-2-go/
I don't think it's weird that the web server could be a bottleneck in a web application (even if it is a database-driven app, as most are).
Of course, if you're making an internal CRUD app that two people are going to use, it's unlikely to matter which stack you use.
- andybak 10y agoI suppose 'weird' wasn't the right word but the vast majority of web development probably isn't constrained by the performance of the language. > if you're making an internal CRUD app that two people are going to use I know you're exaggerating for comic effect but still. You can run sites that have millions of visits a day on a $20/month VPS and still not have to worry about performance - unless you're doing something completely resistant to caching. I don't personally know anyone that has to handle more traffic than that but if you believed the general chatter on HN then that segment of the market doesn't even exist. Going from 30 servers to 2? I might be able to cut my overall hosting bill by a few hundred dollars a year but it's not top of my list of concerns.
- nemothekid 10y ago>There are tons of blog posts about companies that have switched from Ruby or Python to Go and have been able to massively scale down their amount of servers while handling the same load. Here's one example FWIW, these cases don't come down to raw rq/s performance, but are more due to RAM usage.
- insertnickname 10y agoIn the iron.io blog post, they write that their CPU load was drastically reduced as well.