Book Image

Amazon Web Services: Migrating your .NET Enterprise Application

By : Rob Linton
Book Image

Amazon Web Services: Migrating your .NET Enterprise Application

By: Rob Linton

Overview of this book

Amazon Web Services is an Infrastructure as a Service (IaaS) platform in the Cloud, which businesses can take advantage of as their needs demand. The Amazon Cloud provides the enterprise with the flexibility to choose whichever solution is required to solve specific problems, ultimately reducing costs by only paying for what you use. While enterprises understand moving their applications among infrastructure they own and manage, the differences in Amazon's infrastructure bring up specific business, legal, technical, and regulatory issues to get to grips with. This step-by-step guide to moving your Enterprise .NET application to Amazon covers not only the concept, technical design, and strategy, but also enlightens readers about the business strategy and in-depth implementation details involved in moving an application to Amazon. You'll discover how to map your requirements against the Amazon Cloud, as well as secure and enhance your application with AWS. This book helps readers achieve their goal of migrating a .NET Enterprise Application to the AWS cloud. It guides you through the process one step at a time with a sample enterprise application migration. After comparing the existing application with the newly migrated version, it then moves on to explain how to make the hosted application better. It covers how to leverage some of the scalability and redundancy built into the Cloud, and along the way you'll learn about all of the major AWS products like EC2, S3, and EBS.
Table of Contents (19 chapters)
Amazon Web Services: Migrating your .NET Enterprise Application
About the Author
About the Reviewers

What AWS isn't

AWS is not a Platform as a Service (PaaS) provider or Software as a Service (SaaS) provider.

What are these?


A Platform as a Service (PaaS) is a service where you do not manage the underlying infrastructure. An example of this would be Microsoft's Azure framework or Google's App Engine. The benefit of this approach is that you don't have to worry about things such as servers, networks or storage. The downside to this approach is that you have no control over how these services are integrated into your existing infrastructure, and in some cases this isn't even an option.

In this scenario, you would write your application and then deploy it into their controlled environment, letting the PaaS provider manage the underlying infrastructure.


A Software as a Service (SaaS) is a service, that provides an application, rather than a framework. Examples of this would be Microsoft Office Live and, that provide online mail and collaboration services. SaaS services typically are pre-written and do not provide the ability to change minor things such as themes or branding.