‘

This is an important stage in a long process. Microsoft acquired LinkedIn way back in 2016. Even so, as recently as the end of last year, we reported that a move to Azure had been abandoned, which came a few months after it laid off almost 700 LinkedIn staff — the majority in R&D. The blog post is over 3,500 words long, so there’s quite a lot to chew on — and we’re certain that this has been passed through and approved by numerous marketing and management people and scoured of any potentially embarrassing admissions. Some interesting nuggets remain, though. We enjoyed the modest comment that: “However, with the shift to CentOS Stream, users felt uncertain about the project’s direction and the timeline for updates. This uncertainty created some concerns about the reliability and support of CentOS as an operating system.” […]

There are some interesting technical details in the post too. It seems LinkedIn is running on XFS — also the RHEL default file system, of course — with the notable exception of Hadoop, and so the Azure Linux team had to add XFS support. Some CentOS and actual RHEL is still used in there somewhere. That fits perfectly with using any of the RHELatives. However, the post also mentions that the team developed a tool to aid with deploying via MaaS, which it explicitly defines as Metal as a Service. MaaS is a Canonical service, although it does support other distros — so as well as CentOS, there may have been some Ubuntu in the LinkedIn stack as well. Some details hint at what we suspect were probably major deployment headaches. […] Some of the other information covers things the teams did not do, which is equally informative. […]