Short journey to the API Economy

I work with many software vendors who is the new world of cloud computing come in many forms of business partner type as they try to harden their offerings into a something “as-a-Service”.

The starting point is the IBM Cloud Marketplace ( since that is the portal to the cloud for the IBM clients and where they can find IBM Software as a Service (SaaS) offerings and importantly IBM Business Partner SaaS offerings.

The IBM Cloud Marketplace provides a vendor to have a listing from which clients can purchase their offering. This is done by creating a listing and editions (packages) of value that the clients want to buy.

Once integrated into the IBM Cloud Marketplace then there is an option of being integrated INTO IBM Bluemix ( ThisĀ  can provide an additional route to revenue which can be developed by partners by exposing any APIs of their service to other developers i.e. they effectively become one of Bluemix services in the Bluemix Catalogue, which is a subset of the IBM Cloud Marketplace !

In turn those services can run on IBM Softlayer ( and benefit from optimized infrastructure as Bare Metal.

There is more in a couple of chart decks called “Short journey to the API Economy” and another “IBM Softlayer Bluemix Marketplace” can be found in my SlideShare Documents.


Helping drive good cloud service development

I learnt something new today courtesy of the CEO of a partner I met today. Over the last two weeks the subject if micro-services has crept into the discussions and emails. So when the CEO turns out to be an expert on micro-services I asked him to explain.

In his words a micro-service is “a service that can be built in a week of less”. This approach of quick time to market fits very well with the philosophy behind the IBM platform as a service (PaaS) IBM Bluemix. That is, to be able to create and deploy applications quickly, quick time to failure through iterative development and testing and ultimately quick time to market.

The new world of code development for the cloud is an area I am increasingly learning about as I work with partners who want to use IBM Bluemix and evolve content for the IBM Markeplace.

Following on from the idea that micro-services are quick to build is the fact that they are also easierto maintain, debug and support. With many micro-services potentially making up a broader application or service, you now have a set of discrete services that overall enables easier debugging maintenance and support. These many modules are smaller in size and less complex than larger modules therefore, in theory, if one fails it is less likely to destabilise the overall system. Or if it does then it is quick to fix or replace. This concept is know as “anti-fragility”.

Now the notion that something is potentially replaceable is what makes mcro-services and “anti-fragility” all the more interesting as only those micro-services that you know to be reliable and trusted start to be the winners in the market.

Let the market place determine the outcome.