I’ll be honest—when I first heard that IBM decided to base its Maximo Application Suite (MAS) on OpenShift, I didn’t exactly jump for joy. In fact, I think I may have sighed audibly. The concept just didn’t click at first. Why take such a drastic step? Moving Maximo, a trusted, battle-hardened solution, to a containerized platform seemed risky. I mean, sure, we all love a good container, but wouldn’t this alienate the customers who had spent years tweaking and customizing their Maximo environments like some prized, finely-tuned machine?
Like me, several customers hesitated. They raised concerns about the complexity of migrating to OpenShift, the potential for ...