5 ms·
From what I've seen in corporate environments downtime of infrastructure run by internal teams is just as high if not higher than with Github.
by analog 14y ago
From what I've seen in corporate environments downtime of infrastructure run by internal teams is just as high if not higher than with Github.
- hp50g 14y agoThat's anecdotal. My anecdote is that we've run 5 nines for 6 years. We know our shit.
- analog 14y agoWell both of our experiences are anecdotal aren't they. And having a server running doesn't mean that everyone has access to it, one of the issues I've faced is getting approval for VPN access (took a month IIRC) which prevented access to the SVN repo, would not have been an issue with Github. And that org's infrastructure team could probably claim 5 nines uptime as well.
- pifflesnort 14y agoThe organizational delay on VPN provisioning has nothing to do with git, or github, at all. You could have also hosted an external RCS repository over RSH and you wouldn't have had the problem of VPN provisioning being slow. The problem was VPN provisioning, not the source control system.
- analog 14y agoYes, but if the repo was hosted on Github rather than internally then the slow VPN provisioning wouldn't have been an issue. (Good) web services like Github tend to reduce friction, corporate bureaucracies tend to increase friction.
- pifflesnort 14y ago(Good) corporate services wouldn't have had slow VPN provisioning. This has nothing to do with Github, other than the fact that Github would let you end-run all rules about data protection, backups, centralized administration of user access, and everything else that you don't individually have to worry about, but the management and IT at the company you work for does.
- analog 14y ago"centralized administration of user access" This is exactly the sort of thing I'm talking about. Let the team working on the code decide who has access to the code. Not some person in a different part of the country who has no idea what the code does.
- pifflesnort 14y agoThat's a short-sighted selfish view that fails to take into account the responsibilities of the organization at large.
- hp50g 14y agoActually most of our developers can't be trusted with this. We have certain regulatory requirements. We have active directory and its all managed there. If someone needs access, their role defines it. If someone wants access they have to ask.
- hp50g 14y agoActually it would be even worse as we can't risk people pushing our code to their private repo so Mr Firewall goes "no way". Another problem: we dont know which repo we're pushing to at a network level. Code theft is a major problem. Not because the code is crap and we're embarrassed (unlike VMware and Microsoft code leaks), but because its valuable.
- ams6110 14y agoI think that's the exception rather than the norm. Since we're sharing anecdotes, every corporate shop I've worked in tends to stand up services, then once they are working they are not monitored or thought about until there's a problem.
- Jare 14y agoInternal infrastructure may have more total downtime but it's usually managed and scheduled to minimize impact.