In my previous post, I discussed the value of patterns of expertise. We can get even more out of a pattern if we can leverage pattern portability through different cloud environments!
Pattern portability provides greater flexibility by leveraging a specific cloud environment based on your requirements. Let’s consider an example:
My company needs to start a new project, which requires new hardware, new software, and, of course, all the activity to set up and configure the system. The procurement of all these components can take weeks, or even months. Wouldn’t it be great if I could borrow some public cloud environment, have my system team start designing a pattern that fits the requirement, and maybe have my development team start testing the new application against a test environment quickly? And wouldn’t it be even better if I could export everything my teams have done on the public cloud, import it in an on-premise, cloud-based solution without losing anything, and deploy it in minutes?
Or, I may need the opposite. My company may need additional resources to support an expected peak on an application due to a marketing campaign. Buying or finding additional hardware, software, and configuring everything may take weeks. Wouldn’t it be great if I could just export my pattern and import it on a public cloud provider, click on deploy and have a virtual system up and running, configured, and optimized in a few minutes?
This can be done easily if you work with patterns!
Those examples are just ideas. If those samples make you curious, have a look at the Redpaper “Cloud Computing Pattern of Expertise”! The Redpaper covers the value of patterns and how to leverage pattern portability against the different cloud environment provided by IBM.
Feel free to share any comments or thoughts on this post!