IBM Garage Method Applied to Moving to and Modernizing with IBM Cloud
5 min read
By: Franck Boudinet
The beginnings of the IBM Cloud Garage Nice
As a founding member of the IBM Cloud Garage in Nice, France in early February 2015, I could not imagine the incredible experience I would live—working with a growing community of talented developers, designers, and architects, all delivering value to customers through the design, development, and deployment of hundreds of innovative Minimum Viable Products (MVP).
Now, with 15 location opened globally and the ability to “pop-up” pretty much everywhere around the globe, I’m very proud to celebrate the fifth anniversary of the IBM Cloud Garage organization.
Right from the beginning, we engaged with companies of all sizes—from startups like Advansolar (now Mobendi) to global enterprises like Engie—helping them to quickly transform part of their business or offerings leveraging IBM Cloud technologies and services.
We are still delivering a lot of blockchain, Internet of Things, analytics, and cognitive “born-in-the-cloud” solutions. We’ve also expanded our expertise, patterns, and assets to guide our clients’ existing applications to “move-to-cloud” and to better manage their hybrid and multicloud environments by leveraging a variety of IBM Cloud capabilities.
Helping clients "move-to-cloud"
For many of the “move-to-cloud” engagements, we help our clients evolve the architecture of their application, either entirely or partially towards a containerized and microservice architecture, and we often deploy their modernized solution on IBM Cloud Kubernetes Services, IBM Cloud Private (ICP), or a mix of both.
Recently, we engaged a mid-size company in Belgium to transform a .net and Python analytics application running on Windows™ virtual machine to a full-blown, cloud-native application. We helped them harvest all their Python analytics, representing years of effort and intellectual capital for their customers and enable, thanks to a new architecture, better scalability, open API exposure, and the ability to leverage new AI frameworks with Watson ML. This was quite a significant transformation, but with the IBM Garage Method pair-programming approach, we could quickly ramp-up our client’s developers and data scientists to get the first MVP out in a matter of weeks.
Sometimes, “move-to-cloud” does not require heavy lifting on the applications. As an example, I have worked with a large enterprise running in production more than one hundred JBOSS applications. We identified with them four patterns representing more than 80% of their applications and conducted an MVP to containerize four applications (one of each type). We deployed them using helm charts on IBM Cloud Private (ICP), taking care of use cases like scaling-up, scaling down an application, rolling applications updates, and reverting back in order to prepare integration with their DevOps toolchain. We also trained them on using IBM Transformation Advisor as well as Vulnerability Advisor, both running on ICP and IBM Cloud Kubernetes Service. They are now in a much better position to evaluate the benefits, what effort will be needed, and the risks and cost of migrating their entire portfolio and decide at which pace to do it.
I’ll describe in more detail some of these new capabilities related to “move-to-cloud” and to hybrid and multicloud management platform in future blogs. Stay tuned, and like Richard Dawkins says, “By all means let's be open-minded, but not so open-minded that our brains drop out.”
This blog is a part of a series celebrating the fifth anniversary of the IBM Cloud Garage.
To learn more about the IBM Cloud Garage, find our story, resources, and method here. If you would like to see how the IBM Cloud Garage can help your business, schedule a cost-free, four-hour virtual visit with us. We’d love to help you turn that idea into a reality.