Architecting Enterprise Applications In The Cloud
•
7 likes•1,894 views
Architecting Enterprise Applications in the Cloud presentation by Matt Tavis, AWS Solutions Architect, and the Cloud for the Enterprise Event in NY on October 19, 2009
Report
Share
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Architecting Enterprise Applications In The Cloud
Similar to Architecting Enterprise Applications In The Cloud (20)
More from Amazon Web Services
More from Amazon Web Services (20)
Recently uploaded
Recently uploaded (20)
Architecting Enterprise Applications In The Cloud
- 1. Architecting Enterprise Applications in the CloudMatt TavisSolutions Architect
- 2. What Does the Enterprise Application Demand?High AvailabilityManageabilitySecurityMonitoringScalabilityReliability
- 3. TTTS3 ReplicasEC2 RegionsAvailability Zone AAvailability Zone BAvailability Zone CAuto ScalingAmazon CloudWatchElastic Load BalancingNote: Conceptual drawing only. The number of Availability Zones may vary. S3 guarantees 3 or more copies across 2 or more AZs.AWS has the Tools for Enterprise Demands
- 4. Achieving Enterprise Needs is an Agreement between Architecture and InfrastructureLeveraging a scalable, on-demand infrastructure requires an application that can take advantage of it.Corollary: Fork-lifting a broken architecture into the AWS cloud will not make it any betterArchitecture and Infrastructure Must Work Together
- 5. There are Many Paths into the CloudMove to the CloudBuild for the Cloud
- 6. Design for Failure and Nothing FailsLoose Coupling Sets You FreeDesign for DynamismSecurity is EverywhereDon’t Fear ConstraintsLeverage a Variety of Storage ServicesCloud Architecture Lessons Learned
- 7. Never expect your systems to be stableEverything failsHard disksPower suppliesCablingNetwork portsSwitchesLoad-balancersEthernet chipsIO controllersFansEven software failsIf you can add it, it can failDesign for Failure and Nothing Fails
- 8. Elastic IPs enable consistent endpoints and a re-mappableLeverage multiple Amazon EC2 Availability Zones (AZs)Replicate databases and persistence layers across AZsUse real-time monitoring across key access pointsUse Elastic Block Store (EBS) for persistent file systemsSnapshot EBS for disaster recovery and increased persistenceAuto Scaling and Elastic Load Balancing can automatically provision new resourcesUse Amazon CloudWatch to monitor instance healthDesigning for Failure with AWS
- 9. Components should not make no assumptions about the inner workings of other componentsDesign for a jumble of black boxesLoosely coupled systems and AWSDe-coupling systems allows for hybrid models (in-cloud + in-physical data center)Balancing between clusters enables easier scalingUsing queues (Amazon SQS) buffers against failuresLoose Coupling Sets You Free
- 10. Components should not assume the health or location of other componentsBootstrapping and dynamic configuration helps you scale dynamicallyAdd or build management components to enable scale-out and scale-in on-demandDesign for Dynamism
- 11. With AWS, physical security is free, network security is easy, and other security can be addedBuilding secure systems with AWSCreate distinct Security Groups for each Amazon EC2 clusterUse group-based rules for controlling access between layersRestrict external access to specific IP ranges and portsUse strong passwords and certificate-based authenticationEncrypt data stored in Amazon S3Encrypt information transmitted across the wireUse encrypted file systems for sensitive dataSecurity is Everywhere
- 12. Having a flexible, on-demand pool of resources allows for different architectures that remove constraintsDon’t Fear Constraints I need more than xxGB of RAM per instanceDistribute load across multiple instances; use a shared distributed cache I need more than xxK IOPS on my databaseRun multiple read-only copies; sharding; database clustering software My current server specs are better than the EC2 instancesRun more Amazon EC2 instances but only when you need them I need static IPs for my serversBoot scripts that re-configure software from configuration database
- 13. AWS offers a wide variety of storage services designed for reliability, low latency, ease of access, indexing and throughput.Amazon S3 is optimized for easy access to highly durable and available storage of objectsStore persistent data needing durability and easy accessAmazon CloudFront for performancePush popular objects to worldwide edge locationsAmazon SimpleDB for indexing, speed, scale, and simplicityStore small bits of data that have no dependencies, such as metadataAmazon EBS acts like a disk drive for persistent storage with high throughput and basic durabilityStore dynamic content or a traditional RDBMSAmazon EC2 local disk space for transient dataLeverage a Variety of Storage Services
- 14. Deploy internal applications for greater cost savingsDevelopment, test, staging and training environmentsHosting of quick and effective marketing campaign (micro-sites)Faster time to market for new business opportunitiesRecurring or on-demand batch data processing jobsLarge scale analytics (Hadoop)Disaster recoveryLoad testing applications on your own infrastructureWhat Can an Enterprise Do on AWS?
- 15. Sample Architecture:Migrating Your Internal IT Applications
- 16. A typical enterprise application could need:A secure environment that is part of the enterprises’ existing network (Amazon VPC)Computing power (Amazon EC2)Storage capacity for images, videos, backups, files, etc. (Amazon S3)Indexed storage (Amazon SimpleDB)Relational Database (Your favorite on EBS)Messaging between components (Amazon SQS)Load balancing for optimal performanceEnterprise Application Design on AWS
- 17. Create a secure connection between assets and applications within your corporate network and assets and applications that reside in AWSUsers and applications within your existing infrastructure securely interact with assets in AWS as if they were localAmazon VPC Extends Your DatacenterYour existing infrastructureAmazon VPC
- 18. Customer’s isolated AWS resourcesAmazon VPC Architecture10.32.2.0/24Subnets10.32.3.0/2410.32.1.0/24VPN GatewayAmazonWeb ServicesCloudSecure VPN Connection over the InternetExternalCustomersYourNetwork
- 19. Establish subnets to control who and what can access your resourcesConnect your isolated AWS resources and your IT infrastructure via a VPN connectionLaunch AWS resources within the isolated networkUse your existing security and networking technologies to examine traffic to/from your isolated resourcesExtend your existing security and management policies within your IT infrastructure to your isolated AWS resources as if they were running within your infrastructureAmazon VPC Creates an isolated environment within AWS
- 20. Advantages of your on-premises infrastructureEnsure network isolationWorks with your security toolsEmploy your existing identity and authentication infrastructureIntegrates seamlessly with the rest of your infrastructure via VPNPlus, the benefits of a cloud-based infrastructureDon’t get trapped by CapExTrue company-level elasticityLower operational responsibilities and costsSuper-fast provisioning of on-demand resourcesRealize the Best of Both Worlds
- 21. Available nowAmazon EBSSingle AZ in us-east-1Amazon CloudWatchOn-Demand and Reserved InstancesLinux/UNIX and WindowsUpcoming featuresDirect Internet accessMultiple AZsElastic IPsSecurity groupsAmazon DevPayAuto ScalingElastic Load BalancingAmazon VPC: Supported AWS Features
- 22. Internal new employee provisioning applicationA hiring manager visits an internal websiteEnters employee information, including start date, office location, computer type, and so onThe website kicks off a series of workflows on existing systems already deployed within the companyFacilities: setup the office spaceIT: setup the new computerHiring manager: email with forms for employee to fill out…and so on…Spiky usage around Summer (new interns)No internal resources available for the application, so the organization has chosen to deploy in AWSOur Sample Enterprise Application (Old Way)
- 23. Setup the Web Server in Amazon VPCAWS CloudAmazon VPCExisting Network
- 24. FlexibleChoose your programming model, application platform, databases, and operating system stackCost-effective, pay only for what you useScalableAutomatically add and delete resources as they are neededReliableBuilt on the world-class Amazon infrastructureSecureConnection with Amazon VPC ensures that only users within your organization can see your AWS resourcesWeb Server Running on Amazon EC2
- 25. Use Amazon S3 for Raw StorageAWS CloudStore persistent files in Amazon S3 for lower costs, higher reliabilityEncrypt sensitive data
- 26. Use Amazon EBS to Host DatabasesAWS CloudConfigure an Amazon EBS device to host your existing relational database. Snapshots can be automatically backed up to Amazon S3.
- 27. Interact With Existing Corporate SystemsAmazon VPC provides a two-way secure connection so that applications hosted in AWS can communicate with systems hosted in our existing network.
- 28. Amazon SimpleDB can be used as a cost-effective, zero-administration indexed store for your applicationAmazon CloudWatch, Elastic Load Balancing, and Auto-Scaling services enable greater fault-tolerance and scalabilityAmazon Elastic MapReduce can be used to crunch and analyze large amounts of dataAmazon Flexible Payments Service can handle checkout pipelines and payment methodsAmazon Mechanical Turk can be used for tasks best suited for human intervention (e.g., image upload and content approval, database cleansing, etc.)Additional Capabilities
- 29. AWS Management ConsoleNumerous cloud-based third-party providersBMC, RightScale, othersAPI-based control enables existing workflow applications to manage AWS resourcesExisting IT management systems can extend to cloudAmazon VPC enables existing management and operations systems, security policies, etc. to extend to cloud resourcesAmazon CloudWatch provides easy to use monitoringManagement and Operations
- 31. But What if You Have What you Have?But can I use Package X in the AWS Cloud?
Editor's Notes
- This slide discusses the corresponding AWS functionality that we will support at limited public beta launch. Please note that the items under "Launch ++" are other AWS capabilities that we are currently evaluating for operability within VPC, but do not have a date as yet. Direct Internet/AWS access is our most important feature.
- As you can recall, we’ve setup Amazon VPC in the AWS cloud. We’ve also configured a secure connection between our existing network and Amazon VPC. All of our activity inside our VPC and all traffic to and from our existing network and Amazon VPC can be monitored, managed, and secured by all of our existing security apparatus and procedures/policies.We will deploy our web server and full application platform stack on Amazon EC2 instances that are spawned within Amazon VPC.
- Benefits of using Amazon EC2 to host your web application.
- We will host all of our static and large files over on Amazon S3. Things like images, music, PDFs, and the like are best suited for Amazon S3. Amazon S3 provides a low-cost, highly reliable and scalable storage environment for your web applications. We will encrypt this data for security reasons.
- You can host your relational database on top of Amazon EBS. Companies like IBM and Oracle have even enabled license portability so that you can bring your existing database licenses into the AWS cloud.
- As you’ll recall, we want our application to be able to kickoff workflows with a bunch of systems we’re already running internally. While it may make sense, both economically and technically, to eventually migrate these systems into AWS as well, as of right now that isn’t the case. So, we’ll need to be able to have our Employee Provisioning application that is hosted in AWS be able to communicate with our internal systems. With Amazon VPC, this is easy.
- These are some additional AWS features that we could use as part of our application.