Skip to main content

Seasonal or peak loading

Whenever a cloud-based application is accessed by millions of users at the same time, the load on the cloud servers increases. The server should be capable enough to handle all requests at the same time. To handle all the requests, different cloud vendors have different solutions.
 One of the most popular solutions available in the market is Amazon's Elastic Load Balancing. It is a part of Amazon Web Services (AWS).
Elastic Load Balancing handles all the users effectively by distributing the requests made by all the users across different virtual servers (technically called as virtualization). The organisation which anticipates high traffic to its cloud-based application has to create a load balancer (through easily customizing the AWS settings) in one or more of its availability zones. All the traffic to the application first hits the load balancer – which routes the traffic evenly to different virtual servers to process the requests.
Let us take an example of Expedia which is hosted on and utilities Amazon Web Services. There are millions of customers booking flight tickets and hotels through Expedia every single second. All these booking requests come to the load balancers created by Expedia. Then based on the availability of virtual servers, they are routed accordingly to be processed and tickets booked for the customer. Number of ticket bookings would be high especially during holiday and festival seasons like Diwali, Christmas, New Year etc., as a lot of people travel to their native places. AWS offers plenty of services that help Expedia and many such organisations handle seasonal loads.

Comments

Popular posts from this blog

The Seven-Step Model of Migration

Irrespective of the migration approach adopted, the Seven-step Model of Cloud Migration creates a more rational point of view towards the migration process and offers the ability to imbibe several best practices throughout the journey Step 1: Assess Cloud migration assessments are conducted to understand the complexities in the migration process at the code, design and architectural levels. The investment and the recurring costs are also evaluated along with gauging the tools, test cases, functionalities and other features related to the configuration. Step 2: Isolate The applications to be migrated to the cloud from the internal data center are freed of dependencies pertaining to the environment and the existing system. This step cuts a clearer picture about the complexity of the migration process. Step 3: Map Most organisations hold a detailed mapping of their environment with all the systems and applications. This information can be used to distinguish between the ...

Special Permissions in linux

The setuid permission on an executable file means that the command will run as the user owning the file, not as the user that ran the command. One example is the passwd command: [student@desktopX ~]$ ls -l /usr/bin/passwd -rw s r-xr-x. 1 root root 35504 Jul 16 2010 /usr/bin/passwd In a long listing, you can spot the setuid permissions by a lowercase s where you would normally expect the x (owner execute permissions) to be. If the owner does not have execute permissions, this will be replaced by an uppercase S . The special permission setgid on a directory means that files created in the directory will inherit their group ownership from the directory, rather than inheriting it from the creating user. This is commonly used on group collaborative directories to automatically change a file from the default private group to the shared group, or if files in a directory should be...

RequestsDependencyWarning: urllib3 (1.24.1) or chardet (3.0.4) doesn't match a supported version

import tweepy /usr/lib/python2.7/dist-packages/requests/__init__.py:80: RequestsDependencyWarning: urllib3 (1.24.1) or chardet (3.0.4) doesn't match a supported version!   RequestsDependencyWarning) Traceback (most recent call last):   File "<stdin>", line 1, in <module>   File "/usr/local/lib/python2.7/dist-packages/tweepy/__init__.py", line 14, in <module>     from tweepy.api import API   File "/usr/local/lib/python2.7/dist-packages/tweepy/api.py", line 12, in <module>     from tweepy.binder import bind_api   File "/usr/local/lib/python2.7/dist-packages/tweepy/binder.py", line 11, in <module>     import requests   File "/usr/lib/python2.7/dist-packages/requests/__init__.py", line 97, in <module>     from . import utils   File "/usr/lib/python2.7/dist-packages/requests/utils.py", line 26, in <module>     from ._internal_utils import to...

tag