Posts Tagged ‘cloud provider’

Stepping up to the Cloud [infographic]

Migrating to the cloud should be considered as part of an overall business strategy and have a defined business objective addressed. One company might want to leverage cloud services to reduce operating costs and free up IT staff, another might need the ability to rapidly scale capacity, and yet another might need to speed application development.

Keeping the business objective in mind will serve you well as you make the move to the cloud. At each step along the way, you will need to evaluate a provider’s processes, procedures, and abilities to see if they fit your needs. Your choices must be based on how well a provider can support and meet your ultimate objective. With this in mind, there are seven steps to take to ensure success.


Every cloud effort must start by defining the business reason for evaluating and leveraging cloud services. Do you want to avoid large upfront (CAPEX) costs for a new project? Do you need a more agile environment to speed application test and development? Must you scale on demand to be poised to enter a new market? Specifying the business motivator for the move helps determine what capabilities and features you will need from a cloud provider.
The next step is to assess your cloud readiness. In this part of your planning, you need to provide management with information to determine which applications and elements of your operations can make the best use of a cloud environment. When evaluating providers, you will find there are technology differences, as well as variations in operational procedures, responses to problems, governance issues, and the way security is handled.  You need to consider your availability and security requirements for each application.

Once you have decided to transition to the cloud, you need a roadmap to get there. Some applications might be ready for an easy migration. For instance, if you are already running an application in a highly virtualized environment, you might be able to simply move the virtual instances of those applications running on your servers to a cloud provider’s infrastructure. Other applications, such as custom code that is tied to a particular hardware platform, will require more effort. For those applications, you will need to develop a plan of action to get them to the cloud.

Next is the actual migration. As with any major IT undertaking, planning and testing are critical. You need to consider the impact on users. A web commerce site might have a very limited or no time window for disruption. With an internal application you might have the luxury of taking it out of service for a weekend, if users are given proper warning. Once the applications are ported over to a provider’s hardware, you will need to run tests to be sure everything is working and application performance criteria are met.

Over time, you will have the opportunity to fine-tune and optimize your cloud operations. For example, you might leverage a provider’s services that automate provisioning to improve the way you deploy your IT services.

Going hand-in-hand with optimization, you should look at the operational aspects of running your applications in the cloud. After all, cloud is a disruptive technology, and as such, requires new approaches to management and operations. Here, you should work with your provider to develop improved operations management capabilities.

Finally, clouds are not immune to outages. You must work with your provider to plan, execute, implement, and test Business Continuity and Disaster Recovery. These plans need to be documented, communicated and most importantly, tested at least once a year.

Taking these steps, your organization should be able to take advantage of the benefits a cloud approach offers, while helping meet the business goals of the organization.

Designing for Failure Conditions

Today we hear from Chip Childers, product architect for SunGard’s Enterprise Cloud Services and partners with our product management and product engineering teams to drive the overall solution design of the service…CM

I’m a big fan of designing systems to deal with component failures. But let’s be honest, doing that perfectly is pretty darn hard.

In the research paper “Fundamental Concepts of Dependability,” all possible sources of fault conditions have been classified into 16 different categories. In another paper, “Software Architecture Reliability Analysis using Failure Scenarios,” an 8-step failure analysis process is proposed for how to understand a system’s potential failure conditions. All this is about identifying and classifying fault conditions—neither provides any design or logic to resolve the issues

I’m going to go out on a limb, and declare that nobody is doing that type of full and formal analysis for their cloud applications. (OK, perhaps somebody, but certainly not many.)

So that’s the problem in a nutshell. How can you really say that you have fully designed for failure, given all of the possible failure conditions? And for the 90% of the cloud platform population that just want to get their apps built, how much time should they really be spending on solving this problem? And what if you have legacy applications that can’t be designed in a truly “failure proof” way?

This is where an enterprise class cloud infrastructure comes in. An enterprise cloud has the resiliency, redundancy, data restoration, disaster recovery and security capabilities needed to keep your system secure and operating, and the enterprise cloud provider backs those capabilities with a Service Level Agreement. Further, an enterprise cloud also offers 24/7/365 management and monitoring of your virtualized infrastructure.

Failure can not be completely avoided, but you are better off knowing that the underlying platform design was build with resiliency in mind and that you have someone watching your back when things do go wrong.

To what extent could an enterprise cloud transform your company?

Visit our Cloud Solutions Center for videos, white papers and case studies about SunGard’s Enterprise Cloud Services.