Any programmer worth his or her salt has heard of Stack Overflow. Heck, you can’t really call yourself a coder unless you’ve browsed a code snippet or piece of advice on the Jeff Atwood/Joel Spolsky creation. So, what does it take to keep such a heavily trafficked site like Stack Overflow afloat? Here are all the numbers (and photos) you could possibly want.
Photos by Nick Craver
A recent blog post by Nick Craver, Stack Exchange’s systems admin covers — at length — the hardware and software used to run Stack Overflow. It even includes photos of the server gear, if that’s your thing.
If you just want the important numbers, here you go:
209,420,973 (+61,336,090) HTTP requests to our load balancer
66,294,789 (+30,199,477) of those were page loads
1,240,266,346,053 (+406,273,363,426) bytes (1.24 TB) of HTTP traffic sent
569,449,470,023 (+282,874,825,991) bytes (569 GB) total received
3,084,303,599,266 (+1,958,311,041,954) bytes (3.08 TB) total sent
504,816,843 (+170,244,740) SQL Queries (from HTTP requests alone)
It’s common knowledge that the site runs off a Microsoft stack, which includes IIS 8.5 and ASP.Net, and does so very well. In fact, the ship is so tight that while the company has 11 web servers available, it’s mostly overkill:
What do we need to run Stack Overflow? That hasn’t changed much since 2013, but due to the optimizations and new hardware mentioned above, we’re down to needing only 1 web server. We have unintentionally tested this, successfully, a few times. To be clear: I’m saying it works. I’m not saying it’s a good idea. It’s fun though, every time.
And a few snaps of the hardware, a full library of which can be perused on Imgur:
Stack Overflow: The Architecture — 2016 Edition [Nick Craver]