IBM Bluemix

Over the last few weeks I have had many conversations with many partners and clients both big and small, established and startup on the subject of IBM Bluemix.

IBM Bluemix is IBM’s Platform as a Service – a common platform for accelerating new application development and operations and removing infrastructure complexity.

We know that companies of all sizes and types are looking at new ways to develop, deploy and manage applications to rapidly innovate their business models in response to the shifts driven by CAMS (cloud, analytics, mobile and social). Companies are seeking more nimble, lightweight approaches to build new applications and extend existing applications to new channels or what is known as Systems of Engagement.

To do this businesses are concerned with:

  • Speed:        How can I compose new application in days or weeks rather then in months or years?
  • Agility:        How can I improve applications based on analytics and feedback and how can I reallocate investment to areas that are aligned with new business priorities?
  • Multi-Channel:    How can I deliver consistent capabilities across web and mobile and new market requirements?
  • Skills-Gap:    How can I make my development teams more productive without a long and expensive ramp-up to keep pace with the latest technologies while maintaining existing systems?
  • Cost:        How can I get started quickly without requiring a big up-front investment in software, hardware or training.
  • Integration:    How can benefit from all the investment I have made in my existing systems and processes?
  • 4 V’s of Data:    How can manage and make sense of the Volume, Veracity, Variety and Velocity of the data the new systems will generate?

The emergence of Platform as a Service (Paas) which through integration enables Backend as a Service (BaaS) is a key enabler for this.  Backend as a Service is integration into the Systems of Record – the flip side of Systems of Engagement. And key drivers of this are the new generation of developers who play an increasingly important role in the selection and adoption of tools, languages and platforms.

IBM Bluemix answers these needs.  It provides a hosted platform that provides cloud-based development and deployment; pre-configured bundles designed with the essentials for specific domains such as Mobile, Analytics, Connected Car, Commerce; quick-time to market with the ability to rapidly compose applications from a marketplace of IBM and 3rd party services, quick-time to failure allowing developers to explore, learn, test services and create applications fast and quick-time to revenue with billing and procurement services
IBM Bluemix is a unique platform for new services that users require in new markets they are seeing emerge as their opportunities and as threats. Traditional infrastructure services and the associated labour is replaced by smart tools and a platform that removes much of the associated resources.

So sign up at www.bluemix.net and try out the application examples and get involved in the  Bluemix community.  I’d love to know what you think of it.

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.