Why We Chose Rails to Build Gitlab

Re:Why We Chose Rails to Build Gitlab by lixtra on Tuesday January 22, 2019 @06:20PM (#18973788)

> As is so often the case in Rails, it's set up to be nice and simple for a hello world example but little more.

This is just wrong. Rails works very well for 90% of the situations. When it stops working that’s great news:

You’ve won!

You’re Twitter, Facebook or the next big thing. You’ll find talent and money to replace your rails app.

[ Parent | on HN ]

Re:Why We Chose Rails to Build Gitlab by jjeaff on Tuesday January 22, 2019 @10:23PM (#18975378)

I'm having trouble understanding how one could run into a bottleneck only after you reach Facebook or Google or levels. Surely if you have performance issues when you are running on 10,000 machines, you would also have a bottleneck when you start to outgrow your single machine.

[ Parent | on HN ]

Re:Why We Chose Rails to Build Gitlab by hopler on Tuesday January 22, 2019 @10:43PM (#18975490)

Why would you need more than a single machine to serve a request? You need multiple machines to serve many requests concurrently.

[ Parent | on HN ]