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
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
Index

Applying SQS and SNS to our sample application


Now that we have an understanding of both SQS and SNS, let's see how we can apply them to our sample application Waaah. If we look back at the previous chapter, we saw that our sample application was composed of three parts, an SQL Server Database, a WCF Web Service for subscribing and unsubscribing to widgets, and a MVC web application.

In our current architecture, there is only one way to subscribe/unsubscribe to widgets for our Widget Company, and that is through our MVC Web application, Waaah.

While this was the initial design choice for this application, wouldn't it be great if—now that we have migrated our sample application to AWS—we could open up the Subscribe/Unsubscribe service to other applications. So let's look at how we would integrate these two services into our sample application Waaah.

Firstly, let's decouple the WCF Subscription Service from our Subscribe/Unsubscribe service by placing SQS between them. Then let's add another...