Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

What a terribly dishonest and overly-simplistic way of modeling of a distributed system much less a simple web service. found the engineer who, in their own words, “couldn’t code their way out of paper bag.”


If you're serving 40mb a second you don't _need_ a distributed system.

Twitter isn't Netflix.


In the same vein, look at how Plenty of Fish has a huge customer base, and runs on very skimpy hardware. Back in 2006 it had 45M visitors a month, served up over 1B page views a month, all running off three database servers and two load balanced webservers. Guess how many employees? One, Markus Frind[1].

1. http://highscalability.com/plentyoffish-architecture

Of course things have changed, money will do that.


Twitter has about 10x that monthly visitor number just in mDAU. And pof has scaled 100x! (To 100 employees — that seems pretty insane relative the traffic they have going by this weird metric of “amount of data served should roughly equal the number of employees by some ratio”). Comparison also seems a bit lacking given the difference in magnitude also the engineering problems involved (e.g. moderation, botting etc.) Guessing also that creating a dating site is not an exercise in needing a lot of skilled engineering work given it’s been a solved set of problems since the late 90s. Hey Verizon has 132,000 employees — I guess they should only need a fraction of that right since consumer cellular has 2,400?


It’s pretty laughable you believe your own “math.” I guess even serving an actual front end doesn’t factor into your calculations. Hey go build something and you might find out what it actually takes to build/maintain a system of any real consequence instead of doing leet code exercises and smelling your own brain farts.


I guess you're right, you need 10,000 JS engineers to change a light bulb.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: