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


In this chapter, we got a detailed look at how we can perform load testing on our AWS enterprise application by using a Grinder Amazon Machine Image (AMI). We saw the step-by-step process of how we can use Grinder to test our application, and how to modify it to cater for increased infrastructure requirements.

We also got a detailed look at how we can use the features of AWS to perform day-to-day production activities such as implementing new releases and patch/update management into QA environments.

In the last section, we saw that we could start with a running production environment, create a copy in under an hour, and re-run all of the functional and load testing on an exact copy of the hardware being used in production.

In my humble opinion, that's amazing! All for the cost of less than $10/day per server, or in the case of our sample application, it's less than $100/day.

This is the final chapter of our ride together, and I hope you enjoyed it. I've taken you from the very beginning...