> Nobody has (still) never been fired for hiring IBM.
I'm pretty sure I came pretty damn close the one and only time I opted for IBM Cloud (which was called "Bluemix" back then). In fairness, running a PostgreSQL DB in a container wasn't the brightest idea on my part, and it was also my fault for not having backups in place, but when Bluemix ate our entire prod DB, and the multiple-weeks-long back-and-forth with IBM's support only yielded something along the lines of "whoops, that sucks, good luck building a new DB instance from scratch", we rather quickly jumped ship to AWS and never looked back.
I'm sure IBM Cloud is better these days, though it was a bit telling that during my brief time working for IBM my primary job was to build customers' stuff on AWS instead of IBM Cloud. Go figure.
Bluemix wasn’t really IBM Cloud. It was what turned out to be ill-advised backing of Cloud Foundry but a lot of companies did that with a certain degree of public ridicule falling on those who didn’t fall in line.
I'm pretty sure I came pretty damn close the one and only time I opted for IBM Cloud (which was called "Bluemix" back then). In fairness, running a PostgreSQL DB in a container wasn't the brightest idea on my part, and it was also my fault for not having backups in place, but when Bluemix ate our entire prod DB, and the multiple-weeks-long back-and-forth with IBM's support only yielded something along the lines of "whoops, that sucks, good luck building a new DB instance from scratch", we rather quickly jumped ship to AWS and never looked back.
I'm sure IBM Cloud is better these days, though it was a bit telling that during my brief time working for IBM my primary job was to build customers' stuff on AWS instead of IBM Cloud. Go figure.