News for hackers. Stuff that matters.
Re:Scaling GitHub by victork2 on Thursday January 26, 2012 @03:38PM (#3515870)
Well first I said I was in a bad mood.

More seriously, scaling is not simple. Yes products have been introduced or have evolved and simplified greatly the task. But saying that scaling is simple is simply not true. Not everybody do simple web apps, some require very heavy processing behind the scene, Hadoop/ MapReduce operations that have to return complex results in memory constrained environment and all that while maintaining low cost. As an example when Relational database are not sufficient anymore and ACID is not casting its reassuring shadow you can be in trouble if you do things like payroll/ real time process etc...

And again you don't have to be in the top 1000, many companies do not even have a lot of traffic from the general public but have to deal with very hard scaling problem.

Just look at Reddit, they are still having trouble with the Cassandra database which is said to be easiest to scale.

My 5 cents on the question!

Re:Scaling GitHub by getsat on Thursday January 26, 2012 @06:04PM (#3516371)
Reddit is a top 200 site. They do over two billion pageviews/month. A lot of their pages are loading 1,000+ nested replies. They use Postgres as their primary datastore.

Scaling is a solved problem until you're huge if you're not doing something really avante-garde.

Re:Scaling GitHub by adgar on Thursday January 26, 2012 @06:32PM (#3516476)
> A lot of their pages are loading 1,000+ nested replies.

Reddit only shows 200 comments by default. It also used to be you needed Reddit gold to even show 1,000 on the page when it first loads, not sure if you still do (my gold expired)

Re:Scaling GitHub by adgar on Thursday January 26, 2012 @06:31PM (#3516472)
> A lot of their pages are loading 1,000+ nested replies.

Reddit only shows 200 comments by default. It also used to be you needed Reddit gold to even show 1,000 on the page when it first loads.