Nick-Craver

10 ms·

31.
by Nick-Craver 10y ago
We do, but in the specific case of Active Directory, we want to fail over and auth against another data center if the primary is offline. This means for our domain, the local (to the /16) domain controllers are returned first and the
32.
by Nick-Craver 10y ago
If we want a code review on anything risky, we may push a branch or we may just post the commit in chat for review before we build out. Which is chosen depends on how big or blocking the change may be. We ask for code reviews all the time,
33.
by Nick-Craver 10y ago
Perhaps I can add some context on top of the post. All updates are in transactions unless explicitly opted out. Also remember our case is a little special: we have hundreds of the databases with the same schema, what if #328 fails? The fa
34.
by Nick-Craver 10y ago
The problem here is that these services move - so if it's in /etc/hosts, our failover mechanisms (to a DR data center which has a replica server) are severely hindered. We're adding some local cache, but there are some n
35.
Stack Overflow: How We Do Deployment(nickcraver.com)
428 points by Nick-Craver 10y ago|140 comments
36.
Optimization Considerations: Measure at the Browser(nickcraver.com)
1 points by Nick-Craver 11y ago|0 comments
37.
by Nick-Craver 11y ago
This, more than anything. There's no compelling reason to invest in such a move for our situation. We're very interested in how Open Compute progresses, though.
38.
by Nick-Craver 11y ago
These plans are in flux. At a core level (heh), we nee to have libraries ported first anyway . So we're doing that now. Jil, StackExchange.Redis, Dapper, and Sigil are up on NuGet and core compatible today (some as pre-release). Other
39.
by Nick-Craver 11y ago
It's at 1.5TB of data and 200GB of T-Logs these days.
40.
by Nick-Craver 11y ago
I commented a bit here with the architecture post: https://www.reddit.com/r/programming/comments/468p2m/stack_o... But a better answer is: that price keeps changing. We now have a lot of AWS and on-prem
41.
by Nick-Craver 11y ago
To clarify a bit: I meant they are non-essential to serving the sites . If they all went offline, visitors to Stack Overflow would not be aware.
42.
by Nick-Craver 11y ago
In the Stack Overflow cluster, the RAID 0 NVMe contains Stack Overflow database and the SATA SSD RAID 10 holds the others (Mobile, Translations, PRIZM, and Sites). In the Stack Exchange cluster, the RAID 0 NVMe array contains all databases
43.
by Nick-Craver 11y ago
That's coming up! Deployment is the next post in queue: https://trello.com/c/bh4GZ30c/25-deployment
44.
Stack Overflow: The Hardware – 2016 Edition(nickcraver.com)
166 points by Nick-Craver 11y ago|24 comments
45.
by Nick-Craver 11y ago
Ah I see the confusion now. To clarify: we use redis for a great many things, not just serving HTTP requests. For example, we use redis lists and sets to continually recalculate mobile feeds for users - that's roughly 4 billion of the
46.
by Nick-Craver 11y ago
We don't really cache that much, for example: every post, comment, user, etc. on the page is pulled and rendered live. We output cache certain pages for 60 seconds for anonymous users, but it has almost no performance impact (I think i
47.
Stack Overflow: The Architecture – 2016 Edition(nickcraver.com)
328 points by Nick-Craver 11y ago|29 comments
48.
Stack Overflow: A Technical Deconstruction(nickcraver.com)
3 points by Nick-Craver 11y ago|0 comments
49.
by Nick-Craver 11y ago
I wrote this post to make as many developers and sysadmins aware of the (very critical) bug in .Net 4.6 as possible. Please take a minute to read and make anyone deploying (or thinking about deploying) .Net 4.6 aware of the issue. If you ha
50.
Why you should wait on upgrading to .Net 4.6(nickcraver.com)
116 points by Nick-Craver 11y ago|5 comments
51.
by Nick-Craver 11y ago
This isn't true anymore. Octopress uses an older version of Jekyll. If you're on 3.0 (which we're using) has incremental generation. Here's the log of a recent incremental build: [Step 1/3] Jekyll build (11s)
52.
by Nick-Craver 11y ago
This is a photo of the sales area. Developers are downstairs and have their own offices. If you want to browse on streetview, it's here: https://www.google.com/maps/@40.708443,-74.007121,3a,75y,234... Source: I&#x
53.
by Nick-Craver 12y ago
As Kyle says, we were helping our sister company Fog Creek keep their servers online (as well as other people in that facility like Squarespace) because we cared. Our traffic was not being served from that data center and in fact we shut do
54.
by Nick-Craver 12y ago
I can't resist reminding you that 1 command from a sysadmin routing traffic to the wrong network was the cause of the last major outage there :) They are getting much better, as all providers are. They're still just not a fit for
55.
by Nick-Craver 12y ago
It normally would, except the base IIS page is a proper 200 to all requests. The load balancer removes all servers having issues - from HAProxy's point of view things were dandy. As always, we are looking how to adjust our deployment p
56.
by Nick-Craver 12y ago
I haven't had nearly as much experience as George and Shane have with them after initial spin up. I'll get one of those guys to chime in here.
57.
by Nick-Craver 12y ago
Thanks! We honestly do this for us and my mild cabling OCD, but if we can help anyone by sharing the details then it's worth it.
58.
by Nick-Craver 12y ago
The cloud is awesome if you have zero interest whatsoever in hardware. It's not without trade-offs (nor is the other direction), and too many for us - but if it works for you then great I say. We obviously feel very different, and are
59.
by Nick-Craver 12y ago
We have a hot slave at all times for all instances. In the event of a failure the second slave will kick in. All applications are already connected to both servers via the StackExchange.Redis ( https://github.com/StackExchang
60.
Stack Overflow: How we upgrade a live data center(blog.serverfault.com)
213 points by Nick-Craver 12y ago|68 comments

More ›