LinkedIn Is Migrating To Microsoft Azure (venturebeat.com) 53
An anonymous reader writes: LinkedIn today announced it is swapping out its data centers for the public cloud. The Microsoft-owned company is moving its infrastructure to Azure as part of a multi-year migration. VentureBeat sat down with Mohak Shroff, LinkedIn's SVP of engineering, to discuss one of the biggest technological transformations in the company's history. LinkedIn plans to migrate its 645 million members over several years so as not to compromise the site's accessibility, reliability, and performance. "We think probably at least three years till we're done, possibly longer than that," Shroff confirmed. "It will be a gradual migration. We'll see increasing workloads on Azure over time, with a pretty significant inflection point, about a year and a half, two years out from now. And then kind of an accelerated migration post that."
Re: (Score:2)
I don't know how my least favorite task became my specialty but it does pay well.
Cloud migration is a great job to be in right now, and seems to still have many years of runway ahead of it.
In Linkedin's case, being part of Microsoft, they should be able to get good internal support for the migration. I'm sure MS will want to tout it as a success story.
That's one way to get customers. (Score:1)
Just... buy them.
Re: (Score:2, Interesting)
Never? Cloud is fantastic if you also own all the underlying infrastructure, so you can claim it's all cloudy when in truth it's still basically on-prem for you anyway. Bonus points if you can convincingly fudge the chargebacks .
Fixed that for you.
Now if Microsoft put LinkedIn on AWS or Google Cloud and saved money doing it (versus their current on-prem costs), I'd be fucking impressed.
This move to "Azure" is just a shell game, most likely for organizational ease more than anything else.
Re: (Score:1)
Indeed. Now they have bigger Azure usage numbers to report, and a migration story to publish that might trick some shops to self-migrate.
Is it still public cloud? (Score:3)
Is it still public cloud when you run the public cloud?
Re: (Score:2)
Assuming it's the same commodity cloud, then yes, it its.
This had to happen (Score:5, Insightful)
They can list all of the technical reasons they want, but it had to happen because Microsoft owns LinkedIn because they don't need people asking questions like, "Why is LinkedIn running on X instead of your stuff?"
Re: (Score:2)
The amusing thing is that every LinkedIn or LinkedIn Learning (formerly lynda.com) outage for the next five years will likely be blamed on Azure now, whether or not they were the actual cause of the issue.
They probably should have kept this migration quiet until necessary. Sure, some of the IT folks around here will need to know what the new IP address blocks are so we can update our firewall rules accordingly, but it probably didn't need to be public knowledge.
Re: (Score:2)
Ah, yes, have a heart for the poor marketdroids running MS, when have they ever been reticent about puffing up their tiny little chests and bellowing about whatever whizzy they have just afflicted their users with?
Re: (Score:2)
It's ok, I stopped using LinkedIn when MS bought it. I just feel sorry for whoever is left that isn't one of 3 billion indians constantly spamming everyone with friend requests.
Re: (Score:1)
Reminds me of Pixar. Pixar used Linux on their rendering platform, and wasn't shy about taking about it until....Steve Jobs returned to Apple. Then the word "Linux" was dropped from stories when talking about their rendering platform, and then the inevitable switch to Mac OS X.
Re: (Score:2)
MS justified migrating Hotmail to WinNT as an exercise in identifying weaknesses in their platform so they could address them. They knew it was going to be painful and require a lot more hardware, but they wanted to run a large, dynamic web site on WinNT so they could address the issues that customers trying to do the same would face.
Re: (Score:1)
It is recruiting for profit. They could completely fudge the move to Azure as far as I'm concerned, because I'm not the recruiter, I'm one of those people they contact multiple times a day (just today: "hey we've got a great candidate for you" and not 2 hours later from the same recruiter "hey we've got a great position for you"), and they pay for that privilege.
Re: (Score:2)
Re: (Score:1)
LOL. I get those too. My favorite was a requirement for "10 years Informatica experience," but that word "Informatica" has never been on any resume of mine, including the stuff I've put on StinkedIn.
Re: (Score:2)
Will I then get less LinkedIn spam? Perhaps because of Azure outages?
Hopefully.
You appeared in 7 searches today.
Re: (Score:1)
ROFL
Re: (Score:2)
If it's too isolated, how will the users access it?
Re: (Score:1)
Azurely you can’t be serious... (Score:2)
how hard can it be? case study would be fun (Score:1)
how hard can it be to migrate? it's a web site with a database - all the edge stuff is probably handled by a cdn - i figured it ran on a few servers - i would love to see a case study about their architecture and how they migrated it
Re: (Score:1)
Re: (Score:2)
If you waited for this to delete your account, and not deleted when MS bought them, that would be peculiar.
If Azure merely hosted them, MS *might* be able to intervene in ways you don't like. MS ownership means they *can* intervene in ways you don't like.
Azure is the minivan of cloud providers (Score:3, Insightful)
Bad move (Score:2)
Given nobody wants to be anywhere such a toxic cesspool of SPAM and malware moving LinkedIn to Azure is a sure fire way to get Azure blocked.