IBM’s acquisition of Red Hat makes sense on several levels: it adds a high-growth software portfolio to boost software and recurring revenue, and provides IBM with a bit of a ‘halo’ in the tech community, as it now controls the industry’s leading Open Source supplier.
Moving down a level, though, why might this acquisition matter – and to whom? Techaisle’s take on the most important angles that shaped and will determine the success of the deal. (Download Techaisle Take report)
Who does this matter to?
Imagine you are an enterprise with a large legacy infrastructure, possibly in a regulated industry (like financial services or government). You see that IT service delivery is advancing faster outside your walls than within your firm, as other businesses aggressively adopt cloud, Agile, DevOps and containers.
You are motivated to try to integrate these advanced platforms/products/methodologies into your environment as well – to capitalize on the advantages that they can deliver, or because you’re afraid that if you don’t act you’ll be left behind, watching competitors introduce new IT-enabled capabilities faster and at lower cost than you can.
In an organization like this, IT executives are unlikely to want to dive headlong into a deep/committed relationship with a public cloud provider like AWS. They will understand the importance of building a multi-cloud, hybrid IT infrastructure, but will want to manage that environment internally, with a focus on existing capabilities (both installed products and skills). “Cloud first” won’t be a living mandate – it might describe an approach to new and non-critical applications, but won’t be a serious consideration for core systems of record.
Advantages (and some potential pitfalls) of a combined IBM/Red Hat
