← Back to context

Comment by mijoharas

1 day ago

> we started working on path to multi cloud.

Is this microsoft stating that they aren't able to get acceptable reliability from Azure? (I mean, I think a lot of us have heard that, but it's interesting to hear it from microsoft themselves).

It’s pretty damning. But as someone who has used Azure, I buy it.

  • Pretty damming that two Microsoft subsidiaries - GitHub and LinkedIn - either shelved their forced migration to Azure or are looking at non-Azure options.

I think this is more tailored towards enterprise clients that lose money when Github is down, that would probably help with retention.

  • You’d think they could have had the existing GitHub on whatever continue as is (maybe for paying customers) while all the AI new inrush goes to the Azure setup.

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

  • 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 :)

    • 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

      1 reply →

    • > 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.

      2 replies →

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

There was somewhat recently a post here about how priorities, pressure, and management subverted Dave Cutler's vision for Azure (which was to have near zero human involvement) - my Google fu isn't strong enough to find it. Supposedly, someone running over or opening a serial to a rack/VM is now typical operational procedure.

Show HN timing matters more than people think. Monday-Thursday, 9-11am Pacific, is when the front page has the most engaged readers. Weekend posts get less competition but also less engagement.

> multi-cloud

XXXXL size project. May not ever deliver. But if it fails, it will only do so after years grinding through people, resources, etc.

The entire concept of multi cloud is amusing if you think what cloud originally was supposed to be. They could call them meta clouds (might infringe trademarks), and with the current growth trajectory of AI generated code eventually multi-meta-clouds, renamed to beyond-clouds, and then multi-beyond-clounds. I see no limits.