IBM Bluemix

» see bluemix.net as it lived, on the wayback machine

~ the eulogy ~

i never deployed anything to bluemix. by '14 when it launched, my cloud habit was AWS for the heavy stuff and heroku for the throwaway projects, the IBM-flavored PaaS was the enterprise tier i kept seeing in conference keynote slides without anyone i actually knew running an app on it. that was the bluemix problem from the start. the people who chose IBM cloud chose it because the rest of their stack was IBM, the people who chose by ergonomics or pricing chose somewhere else.

this is mostly told from the press releases and the wayback machine. ibm announced bluemix in february 2014 as an open beta at the IBM Pulse conference, general availability landed in july the same year. the bet was open: cloud foundry as the platform layer, softlayer (which IBM had bought in 2013 for 2 billion dollars) as the metal underneath, the brand to compete with elastic beanstalk and azure app service. in those days the PaaS category had a half-dozen serious contenders and bluemix was the enterprise-flavored entry.

the trouble was that no one ranked bluemix above heroku for developer ergonomics or above AWS for raw service depth. ibm's pitch was 'enterprise PaaS with the buildpack ecosystem already wired in' which sounded right on the page and never made it past the first procurement cycle. by mid-2016 the press was describing bluemix as the cloud product ibm wanted to be a contender. the watson integration was the biggest brand-marketing hook and even that did not pull developers from outside the IBM-account base.

the rebrand came on october 30 2017. ibm folded bluemix and softlayer into a single brand called IBM cloud and the bluemix name went into the changelog. the underlying cloud-foundry layer ran on the new brand for a few more years before IBM started deprecating CF in favor of red hat openshift after the july 2019 red hat acquisition. by 2022 the original bluemix product surface was gone in everything but URL fragments.

~ the dossier ~

~ what bluemix was actually for ~

the technical case for bluemix was straightforward: an app developer would push a buildpack-aware git repo, the platform would compile and run it on a managed cluster, the developer would not touch the OS layer. that was the cloud-foundry promise. heroku had it first and made it stick. bluemix added the enterprise-PaaS angle: IBM compliance certifications, private-cloud single-tenant deployment, IBM-branded services for watson and a database-as-a-service tier.

the part that did not land was the developer mindshare. when a startup engineer in 2015 said 'i want to deploy a python app fast' the default was heroku. when they wanted everything around it the default was AWS. bluemix sat between, with the IBM brand that no startup founder wanted on the resume.

~ how it became IBM cloud ~

the october 30 2017 rebrand was framed as consolidation, not retirement. the SoftLayer brand had its own loyal infrastructure customers, bluemix had its own PaaS user base, ibm wanted one cloud name covering both. the rebrand collapsed them into 'IBM Cloud' with bluemix dashboards rebadged in place. for the next two years the bluemix.net domain still worked, mostly as a redirect. enterprise accounts on the bluemix tier kept their workloads running.

the red hat acquisition in july 2019 was the real death blow for cloud foundry under IBM. openshift was kubernetes-native and red hat owned the broader hybrid-cloud story, bluemix-era cloud foundry got deprecated piece by piece. the public-cloud-foundry tier on IBM cloud closed in 2022. the IBM cloud brand is still alive in 2026 but the bluemix-era product is not.

~ what is left of it ~

the cloud foundry foundation itself outlived the IBM bet. pivotal donated the project to the linux foundation in 2015, IBM was one of the founding backers, the open source project kept shipping releases through the late 2010s. by 2024 the cloud-foundry tier in any major public cloud had been deprecated in favor of kubernetes plus a buildpack tool, the buildpack model itself moved into CNCF buildpacks. bluemix as a brand is gone, the architecture pattern it shipped is now the cloud-native default just under different names.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »