Nick Craver

Nick is a developer and SRE on the Core and Site Reliability Engineering teams at Stack Overflow. Nick's passion is performance and efficiency through the entire stack. He does in-depth talks on infrastructure and code approaches used at Stack Overflow, including the story and reasoning behind them.
company November 15, 2016

How We Make Money at Stack Overflow: 2016 Edition

I’m Nick Craver, and you may remember me from my posts about how Stack Overflow does deployment, how we do hardware, and how we built our architecture. What I haven’t explained yet, and what remains a mystery to most developers I meet, is how we make money. I want to do this now not only…
Avatar for Nick Craver
Architecture Lead
engineering May 3, 2016

Stack Overflow: How We Do Deployment – 2016 Edition

We’ve talked about Stack Overflow’s architecture and the hardware behind it. The next most requested topic was Deployment. How do we get code a developer (or some random stranger) writes into production? Let’s break it down. Keep in mind that we’re talking about deploying Stack Overflow for the example, but most of our projects follow…
Avatar for Nick Craver
Architecture Lead
engineering March 29, 2016

Stack Overflow: The Hardware – 2016 Edition

Who loves hardware? Well, I do. If you don’t love hardware then I’d go ahead and close the browser. Still here? Awesome. Or your browser is crazy slow, in which case you should think about some new hardware. I’ve repeated many, many times: performance is a feature. Since your code is only as fast as…
Avatar for Nick Craver
Architecture Lead
engineering February 17, 2016

Stack Overflow: The Architecture – 2016 Edition

To get an idea of what all of this stuff “does,” let me start off with an update on the average day at Stack Overflow. So you can compare to the previous numbers from November 2013, here’s a day of statistics from February 9th, 2016 with differences since November 12th, 2013: 209,420,973 (+61,336,090) HTTP requests…
Avatar for Nick Craver
Architecture Lead