Become a cloud pro! This course provides essential cloud architecture insights for managers and leaders. Get hands-on, no setup, no cleanup, no hassle—ideal for workplace conversations and interviews.

"Cloud Architecture: A Guide To Design & Architect Your Cloud", is a course designed by a group of AWS, Azure Cloud Solution Architects. This course is for Leaders who are thinking about moving their applications to the cloud or for managers what to be a part of the cloud movement one way or the other. The people who generally benefit from this course are Software Development Managers (SDM), IT Managers, Engineering Managers, Technical Program Managers (TPM) and even developers. 

This course essentially gives you all the knowledge you would need to have a well-informed conversation at your workplace or an interview. It is a course for beginners and does not go into details on how you would configure your Load Balancer or how you would set up a bastion host.

Gaurava Gupta

Thanks a lot for such a wonderful course. It helped my understand all the basics. 

Great Course

Nara P

I am a TPM at one of the FANG companies and was looking to learn more about the cloud. This course gave be a good understanding. 

Very good for managers. 

Miklos Rogers

What I especially liked: the lessons are well structured, give a very good understanding. I liked the chapters on Security and the cloud principles. 

This is an excellent course !

Iggy

This was my very first paid course here and it was well worth the money !

This course gave me a head start on the Cloud 

Denver M

This course covers all the key points that were asked at my interview. Hopefully i get the next interview. 

Good overview !

Cloud Architecture: A Guide To Design &  Architect Your Cloud

There are six different migration strategies organizations use to migrate applications to the cloud. These strategies build upon the 5 R’s that Gartner [outlined here](http://www.gartner.com/newsroom/id/1684114) in 2011. 

The most common application migration strategies we see are:


# Re-Hosting

We find that many early net-new development initiatives like startups build cloud-native applications, but in a large legacy migration scenario where the organization is looking to scale its migration quickly to meet a business case, we find that the majority of applications are rehosted. GE Oil & Gas found that, even without implementing any cloud optimizations, it could save roughly 30 percent of its costs by rehosting with a cloud provider. [White paper here.](https://d1.awsstatic.com/whitepapers/Migration/aws-migration-whitepaper.pdf)

Most rehosting can be automated with tools available from cloud providers like AWS, Azure, Oracle, etc although some customers prefer to do this manually as they learn how to apply their legacy systems to the new cloud platform.

Applications are easier to optimize/re-architect once they’re already running in the cloud. Partly because organizations will have developed better skills to do so, and partly because the hard part  of designing the network topology, migrating the application, data, and traffic — has already been done.

# Replatforming
This is what is called  “Lift-and-Shift”. Here you might make a few cloud (or other) optimizations in order to achieve some tangible benefit, but you aren’t otherwise changing the core architecture of the application. You may be looking to reduce the amount of time you spend managing database instances by migrating to a database-as-a-service platform like Amazon Relational Database Service (Amazon RDS) or migrating your application to a fully managed platform like Amazon Elastic Beanstalk.

A large media company migrated hundreds of web servers it ran on-premises to AWS, and, in the process, it moved from WebLogic (a Java application container that requires an expensive license) to Apache Tomcat, an open-source equivalent. This media company saved millions in licensing costs on top of the savings and agility it gained by migrating to AWS.

# Repurchasing
Moving to a different product. Moving a CRM to Salesforce.com, an HR system to Workday, a CMS to Drupal, and so on.

# Refactoring / Re-Architecting
Re-imagining how the application is architected and developed, typically using cloud-native features. This is typically driven by a strong business need to add features, scale, or performance that would otherwise be difficult to achieve in the application’s existing environment.

Customers using this approach are looking to migrate from a monolithic architecture to a service-oriented (or server-less) architecture to boost agility or improve business continuity. This pattern tends to be the most expensive, but, if you have a good product-market fit, it can also be the most beneficial.

# Retire
Determine the parts of your system that are no longer valuable and turn them off, perhaps by conducting an audit with the feature owners to review every part of the environment. It has been found that as much as 10% to 20% of an enterprise IT portfolio is no longer useful, and can simply be turned off. These savings can boost the business case, direct your team’s scarce attention to the things that people use and lessen the surface area you have to secure. 

# Retain
Usually, this means “revisit” or do nothing (for now). Maybe you’re still riding out some depreciation, aren’t ready to prioritize an application that was recently upgraded, or is otherwise not inclined to migrate some applications. You should only migrate what makes sense for the business; and, as the gravity of your portfolio changes from on-premises to the cloud, you’ll probably have fewer reasons to retain.


Learn the common cloud migration strategies. 

Application Migration Strategies

Learn the common cloud migration strategies.

Introduction

Cloud Principles

Operating on the cloud

Security on the Cloud

Understanding the Cloud Architecture

Contact Us

Application Migration Strategies