3 ms·
I think the general consensus for running infrastructure in house isn't superior uptime but superior control. Generally, you don't care if GitHub [or your inho
by opendais 12y ago
I think the general consensus for running infrastructure in house isn't superior uptime but superior control.
Generally, you don't care if GitHub [or your inhouse equivalent] is down when no one is working. Also, if it goes down in the middle of the night and the first guy in fixes it...the difference between 1 man hour down in the morning vs. 20 man hours during the day across an entire team is significant.
There are very valid reasons for both choices.
- skrebbel 12y ago> Generally, you don't care if GitHub [or your inhouse equivalent] is down when no one is working. It is fortunate, then, that all GitHub customers are in the same timezone!
- wFU8oB6RUUSL 12y agoGlobal service should have at least 3 teams (Asia, Europe, America). 4 teams would be better. They can take shifts: Asia team joins the standup meeting of Europe, then goes home. And so on. It might not be affordable for daily works, but perfect for critical issues.
- wFU8oB6RUUSL 12y agoThe feeling of everything is under control...