Welcome!

@CloudExpo Authors: Pat Romanski, Yeshim Deniz, Liz McMillan, Elizabeth White, Zakia Bouachraoui

Related Topics: @CloudExpo, IBM Cloud

@CloudExpo: Blog Post

Mapping Applications to Cloud Domains

It's not always a one-to-one mapping

Among both users and industry professionals, there is no shortage of discussion about mapping application types to the different cloud domains (public, private, hybrid, etc.). In my experience, quite a bit of this discussion centers on breaking down the characteristics and traits of the application (what kind of data does it deal with, where are the external components it connects to, what are the throughput demands, etc.), and mapping those to a distinct cloud domain

I believe that this way of mapping applications to cloud domains overlooks a simple fact: applications have lifecycles. Most of the time organizations map application characteristics to a cloud domain, they do so with the application's production requirements in mind.  This overlooks the development, testing, staging, and probably a host of other phases in the application's journey toward production readiness, and in some cases, it may be best to use different types of cloud environments along this journey.

Consider the case that an IT organization has decided to begin leveraging cloud computing techniques both within their own data center and from the public cloud. For a particular application (maybe an accounts management application), they decide it is best suited for the private cloud due to concerns over the sensitive nature of the data with which it interacts (I'm not endorsing private over public or vice versa, just posing a scenario and decision-making process that is not all that uncommon).

In all likelihood, the decision to use a private cloud for the organization's account management application is indicative of the application's production-level requirements. However, does this necessarily mean the application cannot benefit from a public cloud environment as it moves along to production? Nope.

In a fair number of cases where applications deal with sensitive data, they really only do so in their production environments. During the development and testing process, the application interacts with mock data. The data has the same structure, but the contents are not confidential. If the sensitive nature of the data used by the application was the chief reason  for choosing the private cloud, acknowledging the fact that such data is really only sensitive in a production environments opens the door to the possibility of using a public cloud during the development and test process.

Simply put, one should consider the characteristics of an application and put those characteristics in the context of each phase of the application's lifecycle in order to understand how the application can make use of the cloud. Throughout this process, there are important factors to keep in mind. If you do in fact plan to leverage multiple domains in the delivery of an application, how easy will it be to move the application from one domain to the next? Will your application use the same platforms in the different domains? Can you automate the migration of the application from one lifecycle phase to the next? Can you capture an environment and easily reproduce it in a different cloud domain?

This is a small sample of the kinds of questions one should consider if they plan to leverage multiple cloud domains for a single application. While leveraging multiple domains during the lifecycle of an application may seem to make things more complicated, keep in mind that it can bring substantial benefits. It may mean decreasing the cost of developing and delivering applications, decreasing the time to market, or even enhancing support capabilities of an application already in production. Simply put, do not fall into the trap of making a one-to-one mapping between an application and its cloud domain. Consider the application's lifecycle and construct a plan for using the cloud.

More Stories By Dustin Amrhein

Dustin Amrhein joined IBM as a member of the development team for WebSphere Application Server. While in that position, he worked on the development of Web services infrastructure and Web services programming models. In his current role, Dustin is a technical specialist for cloud, mobile, and data grid technology in IBM's WebSphere portfolio. He blogs at http://dustinamrhein.ulitzer.com. You can follow him on Twitter at http://twitter.com/damrhein.

CloudEXPO Stories
Containers and Kubernetes allow for code portability across on-premise VMs, bare metal, or multiple cloud provider environments. Yet, despite this portability promise, developers may include configuration and application definitions that constrain or even eliminate application portability. In this session we'll describe best practices for "configuration as code" in a Kubernetes environment. We will demonstrate how a properly constructed containerized app can be deployed to both Amazon and Azure using the Kublr platform, and how Kubernetes objects, such as persistent volumes, ingress rules, and services, can be used to abstract from the infrastructure.
Everyone wants the rainbow - reduced IT costs, scalability, continuity, flexibility, manageability, and innovation. But in order to get to that collaboration rainbow, you need the cloud! In this presentation, we'll cover three areas: First - the rainbow of benefits from cloud collaboration. There are many different reasons why more and more companies and institutions are moving to the cloud. Benefits include: cost savings (reducing on-prem infrastructure, reducing data center foot print, reducing IT support costs), enabling growth (ensuring a highly available, highly scalable infrastructure), increasing employee access & engagement (by having collaboration tools that are usable and available globally regardless of location there will be an increased connectedness amongst teams and individuals that will help increase both efficiency and productivity.)
SYS-CON Events announced today that Silicon India has been named “Media Sponsor” of SYS-CON's 21st International Cloud Expo, which will take place on Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. Published in Silicon Valley, Silicon India magazine is the premiere platform for CIOs to discuss their innovative enterprise solutions and allows IT vendors to learn about new solutions that can help grow their business.
We are seeing a major migration of enterprises applications to the cloud. As cloud and business use of real time applications accelerate, legacy networks are no longer able to architecturally support cloud adoption and deliver the performance and security required by highly distributed enterprises. These outdated solutions have become more costly and complicated to implement, install, manage, and maintain.SD-WAN offers unlimited capabilities for accessing the benefits of the cloud and Internet. SD-WAN helps enterprises to take advantage of the exploding landscape of cloud applications and services, due to its unique capability to support all things cloud related.
Founded in 2000, Chetu Inc. is a global provider of customized software development solutions and IT staff augmentation services for software technology providers. By providing clients with unparalleled niche technology expertise and industry experience, Chetu has become the premiere long-term, back-end software development partner for start-ups, SMBs, and Fortune 500 companies. Chetu is headquartered in Plantation, Florida, with thirteen offices throughout the U.S. and abroad.