121–130 of 197 posts
Such incidents remind me of 2 things 1. No matter what 99.99999999% availability a service provides, its utterly useless if the time to get back up is unacceptable. 2. Do not have remote services, which you cannot fully control to be a part of your run time deployments.
Uptime % includes time to recovery. Since you're not up if you're still recovering...
Earlier quoted context omitted.
How is the GitHub marketplace a runtime dependency? Code review, project management, build bots or whatever else should NOT affect the availability of your website.
Sure, if you measure uptime of your business and dev team by whether you're serving pages. I wouldn't. If Github being down means you're not fixing your site today, I'd call it a runtime dependency.
What do people do to get around this? Run my own git server like the good 'ol days? Github has become a central source of failure for us now...
Earlier quoted context omitted.
Kind of? How many servers did the average app depend on in 1998? 1? Get dual HD and you were in decent shape. Compare to a modern microservice app, that maybe depends on 100 internal services and 4-5 external services. A lot of things need to go right or mostly right for things to function.
Sounds like an argument against micro services?
Such incidents remind me of 2 things 1. No matter what 99.99999999% availability a service provides, its utterly useless if the time to get back up is unacceptable. 2. Do not have remote services, which you cannot fully control to be a part of your run time deployments.
Uptime % includes time to recovery. Since you're not up if you're still recovering...
Earlier quoted context omitted.
Gitea[0] is extremely simple to host, if you want a self-hosted solution that's not as heavy as gitlab. [0] https://gitea.io
Gitea sadly has some issues (for example, the "Public Activity" tab on user profiles 500's atm: https://try.gitea.io/crackedmind?tab=activity ; it throws 500's everywhere once you throw on a modern Xeon more than 30 users/second at it, because it doesn't cache database accesses, at all, etc).
if only we had a decentralized version control system...