---
title: "IBM's Cast Iron Fix for API Proliferation"
date: 2010-05-03T19:15:32Z
modified: 2010-05-03T19:15:32Z
permalink: "https://redmonk.com/jgovernor/ibms-cast-iron-fix-for-api-proliferation/"
type: post
status: publish
excerpt: ""
wpid: 2734
categories:
  - Uncategorized
timestamp: 2010-05-03T19:15:32Z
tags:
  - Uncategorized
---

I hate it when that happens. Just came into the analyst general session and IBM WebSphere CTO Gennaro Cuomo reminded me of Redmonk’s own research agenda and how it relates to IBM’s decision to acquire Cast Iron Systems.

Here is the thing – one of Stephen’s [predictions for 2010](http://redmonk.com/sogrady/2009/11/12/2010-predictions/) was that API proliferation will become a real problem this year. Clearly it already is. I had to talked to Jerry at length about the need to take a registry/repository approach to Cloud-based APIs last year. Well it seems that’s the space Cast Iron is in. At first glance I was thinking about the deal in more traditional middleware terms- adapters and integration.

But in fact Cast Iron may be way more interesting that that. Its an API management platform – IBM will do the work to track all these APIs and help organisations build apps that target them. Unlike many web companies enterprises don’t really have time to concentrate on tracking API changes.

Holy crap. I just realised its also an amazing data play. Cast Iron effectively instruments the world of APIs. IBM is going to know exactly what’s going on in cloud development- what’s hot and what’s not. This really could be a transformative acquisition.

disclosure: IBM is a client.