Sometimes it is. There are some incredibly brute force yet simple and elegant pattern that power some of the biggest scale system you could think of.
It is relatively easy to scale a collection of simple things to extreme and exhibit complex behavior together. It is a lot harder to scale something complex to extreme. But too many times the latter is the default - designed wrong from the ground up and stuck in scaling hell.
It was pretty easy before October 2018, when Microsoft bought them:
https://www.githubstatus.com/uptime?page=31
Not saying they are doing a particular good job but its not as simple as "paying more for bigger machines" and be done with it.
Scaling to human use vs automated/agentic use is a very different thing.
Github has had horrible uptime for years, before agentic use was a thing. The killer was Microsoft.
1 reply →
Do we know this is the predominant reason?
To be fair, that was 8 years ago. Github now has all that days and users + 8 years of data and users.
Sometimes it is. There are some incredibly brute force yet simple and elegant pattern that power some of the biggest scale system you could think of.
It is relatively easy to scale a collection of simple things to extreme and exhibit complex behavior together. It is a lot harder to scale something complex to extreme. But too many times the latter is the default - designed wrong from the ground up and stuck in scaling hell.
They’re focused and hiring right and managing right, but this is just so difficult it’s bound to go down?
If Google owned GitHub would they be better positioned to scale?