{"id":1640,"date":"2013-09-30T02:19:12","date_gmt":"2013-09-30T07:19:12","guid":{"rendered":"http:\/\/www.migrate2cloud.com\/blog\/?p=1640"},"modified":"2016-03-21T02:42:12","modified_gmt":"2016-03-21T07:42:12","slug":"web-2-0-application-architecture-template","status":"publish","type":"post","link":"https:\/\/www.migrate2cloud.com\/blog\/web-2-0-application-architecture-template\/","title":{"rendered":"Web 2.0 application architecture Template"},"content":{"rendered":"

Application created for a Startup based in Chicago<\/h4>\n

The term ‘Load Balancer’ is quite self-explanatory, it balances the load on application servers behind it. There can be ‘n’<\/em> number of application servers behind the Load Balancer \u00a0(LB) which would not be directly facing the end users.<\/p>\n


\nThe LB balances the load caused by the requests from end users accessing the web application, among different application servers with various scheduling –\u00a0balancing algorithms. So as the load is balanced among different application servers, the performance of the portal will be far better if the same was served using a single application server. But now if there is only one LB in place, that point makes SPOF (Single Point Of Failure) in the whole architecture. So in-order to overcome this we can have 2 or more LB. But what happens if one LB is facing some issue and is no more capable of handling the requests? In case of 2 LB based deployment architecture this again makes SPOF. In-order to overcome this we can configure ‘Automation’ at the LB layer in such a way that when a LB becomes unhealthy it will get replaced with a fresh LB without any manual intervention.<\/p>\n

\"load<\/a><\/p>\n

For automation we are using “AutoScaling” a service offered by AWS(Amazon Web Services) and also the architecture is deployed in AWS. Auto Scaling allows us to scale our Amazon EC2 capacity up or down automatically according to conditions we define. Here we have setup a custom LB in EC2 with an application tend to work as LB. A job is also configured in the same instance in such a way that it uploads the application’s configuration file to S3 at certain intervals of time. A base AMI with this setup is taken and Autoscaling is configured above this.<\/p>\n

Autoscaling is configured in such a way that there will be always ‘n’ number of LB instances in the LB layer. As of now we don\u2019t mess with DNS level, as it is maintained with constant values(IP\u2019s). Configuration of Autoscaling includes instance type, security groups, availability zone, key-pair, userdata etc. As autoscaling is configured to always have \u2018n\u2019 number of LB instances, whenever AWS detects that our LB instance is unhealthy it will get terminated and a new LB instance will be launched in it\u2019s place via Autoscaling and the corresponding public IP of the terminated one will get attached and latest configuration on which the LB application was working will get downloaded to the new instance as per the settings made in user-data and starts working on it\u2019s basis. In doing so no change has to be done at DNS level. During this process there won\u2019t be any outage for the portal as other LB\u2019s will be available to serve the end-user requests. Whenever there is a major change at LB application level it is possible to modify Autoscaling configuration accordingly.<\/p>\n","protected":false},"excerpt":{"rendered":"

Application created for a Startup based in Chicago The term ‘Load Balancer’ is quite self-explanatory, it balances the load on application servers behind it. There can be ‘n’ number of application servers behind the Load Balancer \u00a0(LB) which would not be directly facing the end users.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[34],"tags":[235,221,237,98,239,127,215,243,242,144,137,238,240,44,130,232,236,136,241,126,125,234,233],"class_list":["post-1640","post","type-post","status-publish","format-standard","hentry","category-amazon-ec2","tag-amazon-elastic-compute-cloud","tag-amazon-web-services","tag-application-server","tag-autoscaling","tag-city-chicago","tag-cloud-computing","tag-cloud-infrastructure","tag-company-product","tag-company-amazon-web","tag-company-amazon-com","tag-department-stores-nec","tag-dns","tag-lb","tag-load-balancing","tag-loadbalancer","tag-network-management","tag-single-point-of-failure","tag-technologyinternet","tag-web-application","tag-web-application-architecture","tag-web-based-application","tag-web-hosting","tag-web-services"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t