Seems pretty sensible to not rely on a single provider for their large complex system?

embedding-shape 2 hours ago | parent | next [-]

Man, you should have been there 6 months ago when they decided to start tearing down GitHub's own data centers and move everything exclusively to Azure. Seems they themselves realized this after they started moving, but imagine if you could have helped them realize this before they even started :)

▲

benterix 2 hours ago | parent | next [-]

> Seems they themselves realized this after they started moving

I guess most people at Github knew exactly it makes no sense but they didn't really have a choice. Maybe some voiced their statement, got "we hear you" in response and were told to proceed anyway.

	▲	embedding-shape 2 hours ago \| parent [-]
		Yeah, I don't know how it went down, but I also know exactly how it went down: Microsoft Execs: Everyone needs to move to Azure! GitHub developers: But Azure is not gonna be able to handle our load, we literally have our own data centers! Microsoft Execs: Sure, but you're Microsoft now, please publish blog post about how in half a year you'll be 100% on Azure. Few months later... GitHub Developer: We've tried our best, users are leaving in droves and Azure can't keep up! Microsoft Execs: Ok fine, you can use something else too, but only if you mainly use Azure and continue publishing blog posts about how great Azure is.

▲

nextaccountic 2 hours ago | parent | prev [-]

Made me think. Why not convert Github datacenters into Azure datacenters that have Github as their sole customer?

Then it's up to Azure how they will manage this

▲

mijoharas 3 hours ago | parent | prev | next [-]

I mean, amazon (shopping, along with prime video e.t.c.) runs on AWS.

▲

ksimukka 2 hours ago | parent | next [-]

When I was at AWS, retail was not yet running on AWS. Has that changed?

Prime video does use some AWS services, but live and on-demand are two entirely different beasts.

▲

mijoharas 2 hours ago | parent [-]

Really? I thought retail was. It's been almost a decade since I worked at prime video but I think everything was running on AWS. (Some things didn't use brazil etc, but I think all the servers etc. were on AWS)

	▲	malfist an hour ago \| parent [-]
		It's a distinction without a difference. All new development is nAWS (native AWS) legacy is mAWS (not sure about the acronym) which is still AWS under the hood and is mostly just a pool of EC2 instances with preconfigured networks. Nothing made in the last five or six years is on maws, and amazon is a micro service shop so things are always being built new. If you joined today there's a good chance you'd join a team without any maws infra

▲

jasoncartwright 3 hours ago | parent | prev [-]

Prime video uses a non-AWS CDN when I watch football on it here in the UK

	▲	farfatched 2 hours ago \| parent [-]
		The BBC were unable to find a single CDN that could serve the UK during its peak football matches. https://www.bbc.co.uk/webarchive/https%3A%2F%2Fwww.bbc.co.uk...

▲

cyanydeez 3 hours ago | parent | prev [-]

This isn't a mom and pop shop. They have locations all over the world: https://datacenters.microsoft.com/

There's no intrinsic reason they should be vulnerable to themselves.

	▲	farfatched 2 hours ago \| parent \| next [-]
		+1. Multi-cloud is typically done for vendor independence. But Github don't have that rationale.
	▲	jasoncartwright 3 hours ago \| parent \| prev [-]
		That website (for me) uses Cloudflare via WPEngine, which also isn't Azure