UNIT V

CLOUD COMPUTING

definition of cloud computing:

Cloud computing is on-demand access, via the internet, to computing resources—applications, servers
(physical servers and virtual servers), data storage, development tools, networking capabilities, and more
—hosted at a remote data center managed by a cloud services provider (or CSP). The CSP makes these
resources available for a monthly subscription fee or bills them according to usage.

Cloud computing enables customers to use infrastructure and applications via the internet, without
installing and maintaining them on-premises.

Compared to traditional on-premises IT, and depending on the cloud services you select, cloud
computing helps do the following:

 Lower IT costs: Cloud lets you offload some or most of the costs and effort of purchasing,
installing, configuring, and managing your own on-premises infrastructure.

 Improve agility and time-to-value: With cloud, your organization can start using enterprise
applications in minutes, instead of waiting weeks or months for IT to respond to a request,
purchase and configure supporting hardware, and install software. Cloud also lets you empower
certain users—specifically developers and data scientists—to help themselves to software and
support infrastructure.

 Scale more easily and cost-effectively: Cloud provides elasticity—instead of purchasing excess
capacity that sits unused during slow periods, you can scale capacity up and down in response to
spikes and dips in traffic. You can also take advantage of your cloud provider’s global network to
spread your applications closer to users around the world.

Characteristic of cloud:
There are many characteristics of Cloud Computing here are few of them :
1. On-demand self-services: The Cloud computing services does not require any human
administrators, user themselves are able to provision, monitor and manage computing resources as
needed.
2. Broad network access: The Computing services are generally provided over standard networks
and heterogeneous devices.
3. Rapid elasticity: The Computing services should have IT resources that are able to scale out and in
quickly and on as needed basis. Whenever the user require services it is provided to him and it is
scale out as soon as its requirement gets over.
4. Resource pooling: The IT resource (e.g., networks, servers, storage, applications, and services)
present are shared across multiple applications and occupant in an uncommitted manner. Multiple
clients are provided service from a same physical resource.
5. Measured service: The resource utilization is tracked for each application and occupant, it will
provide both the user and the resource provider with an account of what has been used. This is done
for various reasons like monitoring billing and effective use of resource.
6. Multi-tenancy: Cloud computing providers can support multiple tenants (users or organizations)
on a single set of shared resources.
7. Virtualization: Cloud computing providers use virtualization technology to abstract underlying
hardware resources and present them as logical resources to users.
8. Resilient computing: Cloud computing services are typically designed with redundancy and fault
tolerance in mind, which ensures high availability and reliability.
9. Flexible pricing models: Cloud providers offer a variety of pricing models, including pay-per-use,
subscription-based, and spot pricing, allowing users to choose the option that best suits their needs.
10. Security: Cloud providers invest heavily in security measures to protect their users’ data and
ensure the privacy of sensitive information.
11. Automation: Cloud computing services are often highly automated, allowing users to deploy and
manage resources with minimal manual intervention.
12. Sustainability: Cloud providers are increasingly focused on sustainable practices, such as energy-
efficient data centers and the use of renewable energy sources, to reduce their environmental
impact.

Cloud Deployment Models:

Cloud Deployment Model functions as a virtual computing environment with a deployment architecture
that varies depending on the amount of data you want to store and who has access to the infrastructure.
Types of Cloud Computing Deployment Models
The cloud deployment model identifies the specific type of cloud environment based on ownership,
scale, and access, as well as the cloud’s nature and purpose. The location of the servers you’re utilizing
and who controls them are defined by a cloud deployment model. It specifies how your cloud
infrastructure will look, what you can change, and whether you will be given services or will have to
create everything yourself. Relationships between the infrastructure and your users are also defined by
cloud deployment types. Different types of cloud computing deployment models are described below.
Public Cloud
The public cloud makes it possible for anybody to access systems and services. The public cloud may
be less secure as it is open to everyone. The public cloud is one in which cloud infrastructure services
are provided over the internet to the general people or major industry groups. The infrastructure in this
cloud model is owned by the entity that delivers the cloud services, not by the consumer. It is a type of
cloud hosting that allows customers and users to easily access systems and services. This form of cloud
computing is an excellent example of cloud hosting, in which service providers supply services to a
variety of customers. In this arrangement, storage backup and retrieval services are given for free, as a
subscription, or on a per-user basis. For example, Google App Engine etc.
Advantages of the Public Cloud Model
 Minimal Investment: Because it is a pay-per-use service, there is no substantial upfront fee,
making it excellent for enterprises that require immediate access to resources.
 No setup cost: The entire infrastructure is fully subsidized by the cloud service providers, thus
there is no need to set up any hardware.
 Infrastructure Management is not required: Using the public cloud does not necessitate
infrastructure management.
 No maintenance: The maintenance work is done by the service provider (not users).
 Dynamic Scalability: To fulfill your company’s needs, on-demand resources are accessible.
Disadvantages of the Public Cloud Model
 Less secure: Public cloud is less secure as resources are public so there is no guarantee of high-
level security.
 Low customization: It is accessed by many public so it can’t be customized according to personal
requirements.
Private Cloud
The private cloud deployment model is the exact opposite of the public cloud deployment model. It’s a
one-on-one environment for a single user (customer). There is no need to share your hardware with
anyone else. The distinction between private and public clouds is in how you handle all of the
hardware. It is also called the “internal cloud” & it refers to the ability to access systems and services
within a given border or organization. The cloud platform is implemented in a cloud-based secure
environment that is protected by powerful firewalls and under the supervision of an organization’s IT
department. The private cloud gives greater flexibility of control over cloud resources.

Advantages of the Private Cloud Model

 Better Control: You are the sole owner of the property. You gain complete command over service
integration, IT operations, policies, and user behavior.
 Data Security and Privacy: It’s suitable for storing corporate information to which only
authorized staff have access. By segmenting resources within the same infrastructure, improved
access and security can be achieved.
 Supports Legacy Systems: This approach is designed to work with legacy systems that are unable
to access the public cloud.
 Customization: Unlike a public cloud deployment, a private cloud allows a company to tailor its
solution to meet its specific needs.
Disadvantages of the Private Cloud Model
 Less scalable: Private clouds are scaled within a certain range as there is less number of clients.
 Costly: Private clouds are more costly as they provide personalized facilities.
Hybrid Cloud
By bridging the public and private worlds with a layer of proprietary software, hybrid cloud computing
gives the best of both worlds. With a hybrid solution, you may host the app in a safe environment while
taking advantage of the public cloud’s cost savings. Organizations can move data and applications
between different clouds using a combination of two or more cloud deployment methods, depending on
their needs.
Advantages of the Hybrid Cloud Model
 Flexibility and control: Businesses with more flexibility can design personalized solutions that
meet their particular needs.
 Cost: Because public clouds provide scalability, you’ll only be responsible for paying for the extra
capacity if you require it.
 Security: Because data is properly separated, the chances of data theft by attackers are
considerably reduced.
Disadvantages of the Hybrid Cloud Model
 Difficult to manage: Hybrid clouds are difficult to manage as it is a combination of both public
and private cloud. So, it is complex.
 Slow data transmission: Data transmission in the hybrid cloud takes place through the public
cloud so latency occurs.
Community Cloud
It allows systems and services to be accessible by a group of organizations. It is a distributed system
that is created by integrating the services of different clouds to address the specific needs of a
community, industry, or business. The infrastructure of the community could be shared between the
organization which has shared concerns or tasks. It is generally managed by a third party or by the
combination of one or more organizations in the community.
Advantages of the Community Cloud Model
 Cost Effective: It is cost-effective because the cloud is shared by multiple organizations or
communities.
 Security: Community cloud provides better security.
 Shared resources: It allows you to share resources, infrastructure, etc. with multiple organizations.
 Collaboration and data sharing: It is suitable for both collaboration and data sharing.
Disadvantages of the Community Cloud Model
 Limited Scalability: Community cloud is relatively less scalable as many organizations share the
same resources according to their collaborative interests.
 Rigid in customization: As the data and resources are shared among different organizations
according to their mutual interests if an organization wants some changes according to their needs
they cannot do so because it will have an impact on other organizations.
Multi-Cloud
We’re talking about employing multiple cloud providers at the same time under this paradigm, as the
name implies. It’s similar to the hybrid cloud deployment approach, which combines public and private
cloud resources. Instead of merging private and public clouds, multi-cloud uses many public
clouds. Although public cloud providers provide numerous tools to improve the reliability of their
services, mishaps still occur. It’s quite rare that two distinct clouds would have an incident at the same
moment. As a result, multi-cloud deployment improves the high availability of your services even
more.
Advantages of the Multi-Cloud Model
 You can mix and match the best features of each cloud provider’s services to suit the demands of
your apps, workloads, and business by choosing different cloud providers.
 Reduced Latency: To reduce latency and improve user experience, you can choose cloud regions
and zones that are close to your clients.
 High availability of service: It’s quite rare that two distinct clouds would have an incident at the
same moment. So, the multi-cloud deployment improves the high availability of your services.
Disadvantages of the Multi-Cloud Model
 Complex: The combination of many clouds makes the system complex and bottlenecks may occur.
 Security issue: Due to the complex structure, there may be loopholes to which a hacker can take
advantage hence, makes the data insecure.

Cloud service models:

There are the following three types of cloud service models -

1. Infrastructure as a Service (IaaS)

2. Platform as a Service (PaaS)
3. Software as a Service (SaaS)

Infrastructure as a Service (IaaS)

IaaS is also known as Hardware as a Service (HaaS). It is a computing infrastructure managed over the
internet. The main advantage of using IaaS is that it helps users to avoid the cost and complexity of
purchasing and managing the physical servers.

Characteristics of IaaS

There are the following characteristics of IaaS -

o Resources are available as a service

o Services are highly scalable
 o Dynamic and flexible
o GUI and API-based access
o Automated administrative tasks

Example: DigitalOcean, Linode, Amazon Web Services (AWS), Microsoft Azure, Google Compute
Engine (GCE), Rackspace, and Cisco Metacloud.

Platform as a Service (PaaS)

PaaS cloud computing platform is created for the programmer to develop, test, run, and manage the
applications.

Characteristics of PaaS

There are the following characteristics of PaaS -

o Accessible to various users via the same development application.

o Integrates with web services and databases.
o Builds on virtualization technology, so resources can easily be scaled up or down as per the
organization's need.
o Support multiple languages and frameworks.
o Provides an ability to "Auto-scale".

Example: AWS Elastic Beanstalk, Windows Azure, Heroku, [Link], Google App Engine, Apache
Stratos, Magento Commerce Cloud, and OpenShift.

Software as a Service (SaaS)

SaaS is also known as "on-demand software". It is a software in which the applications are hosted by a
cloud service provider. Users can access these applications with the help of internet connection and web
browser.

Characteristics of SaaS

There are the following characteristics of SaaS -

o Managed from a central location

o Hosted on a remote server
o Accessible over the internet
o Users are not responsible for hardware and software updates. Updates are applied automatically.
 o The services are purchased on the pay-as-per-use basis

Example: BigCommerce, Google Apps, Salesforce, Dropbox, ZenDesk, Cisco WebEx, ZenDesk, Slack,
and GoToMeeting.

Driving factors and challenges of cloud:

Top 15 Challenges of Cloud Computing

Cloud computing is a hot topic at the moment, and there is a lot of ambiguity when it comes to
managing its features and resources. Technology is evolving, and as companies scale up, their need to
use the latest Cloud frameworks also increases. Some of the benefits introduced by cloud solutions
include data security, flexibility, efficiency, and high performance. Smoother processes and improved
collaboration between enterprises while reducing costs are among its perks. However, the Cloud is not
perfect and has its own set of drawbacks when it comes to data management and privacy concerns.
Thus, there are various benefits and challenges of cloud computing. The list below discusses some of
the key challenges in the adoption of cloud computing.

The top 15 cloud computing challenges and problems include:

1. Data Security and Privacy

Data security is a major concern when working with Cloud environments. It is one of the major
challenges in cloud computing as users have to take accountability for their data, and not all Cloud
providers can assure 100% data privacy. Lack of visibility and control tools, no identity access
management, data misuse, and Cloud misconfiguration are the common causes behind Cloud privacy
leaks. There are also concerns with insecure APIs, malicious insiders, and oversights or neglect in
Cloud data management.

Solution: Configure network hardware and install the latest software updates to prevent security
vulnerabilities. Using firewalls, antivirus, and increasing bandwidth for Cloud data availability are
some ways to prevent data security risks.
2. Multi-Cloud Environments

Common cloud computing issues and challenges with multi-cloud environments are - configuration
errors, lack of security patches, data governance, and no granularity. It is difficult to track the security
requirements of multi-clouds and apply data management policies across various boards.

Solution: Using a multi-cloud data management solution is a good start for enterprises. Not all tools
will offer specific security functionalities, and multi-cloud environments grow highly sophisticated
and complex. Open-source products like Terraform provide a great deal of control over multi-cloud
architectures.

3. Performance Challenges

The performance of Cloud computing solutions depends on the vendors who offer these services to
clients, and if a Cloud vendor goes down, the business gets affected too. It is one of the major
challenges associated with cloud computing.

Solution: Sign up with Cloud Service Providers who have real-time SaaS monitoring policies.

The Cloud Solution Architect Certification training addresses all Cloud performance issues and
teaches learners how to mitigate them.

4. Interoperability and Flexibility

Interoperability is a challenge when you try to move applications between two or multiple Cloud
ecosystems. It is one of the challenges faced in cloud computing. Some common issues faced are:

 Rebuilding application stacks to match the target cloud environment's specifications

 Handling data encryption during migration
 Setting up networks in the target cloud for operations
 Managing apps and services in the target cloud ecosystem
Solution: Setting Cloud interoperability and portability standards in organizations before getting to
work on projects can help solve this problem. The use of multi-layer authentication and authorization
tools is also encouraged for account verifications in public, private, and hybrid cloud ecosystems.
5. High Dependence on Network

Lack of sufficient internet bandwidth is a common problem when transferring large volumes of
information to and from Cloud data servers. It is one of the various challenges in cloud computing.
Data is highly vulnerable, and there is a risk of sudden outages. Enterprises that want to lower
hardware costs without sacrificing performance need to ensure there is high bandwidth, which will
help prevent business losses from sudden outages.

Solution: Pay more for higher bandwidth and focus on improving operational efficiency to address
network dependencies.

6. Lack of Knowledge and Expertise

Organizations are finding it tough to find and hire the right Cloud talent, which is another common
challenge in cloud computing. There is a shortage of professionals with the required qualifications in
the industry. Workloads are increasing, and the number of tools launched in the market is increasing.
Enterprises need good expertise in order to use these tools and find out which ones are ideal for them.

Solution: Hire Cloud professionals with specializations in DevOps and automation

7. Reliability and Availability

High unavailability of Cloud services and a lack of reliability are two major concerns in these
ecosystems. Organizations are forced to seek additional computing resources in order to keep up with
changing business requirements. If a Cloud vendor gets hacked or affected, the data of organizations
using their services gets compromised. It is another one of the many cloud security risks and
challenges faced by the industry.

Solution: Implementing the NIST Framework standards in Cloud environments can greatly improve
both aspects.

8. Password Security

Account managers use the same passwords to manage all their Cloud accounts. Password management
is a critical problem, and it is often found that users resort to using reused and weak passwords.
Solution: Use a strong password management solution to secure all your accounts. To further improve
security, use Multifactor Authentication (MFA) in addition to a password manager. Good cloud-based
password managers alert users of security risks and leaks.

9. Cost Management

Even though Cloud Service Providers (CSPs) offer a pay-as-you-go subscription for services, the costs
can add up. Hidden costs appear in the form of underutilized resources in enterprises.

Solution: Auditing systems regularly and implementing resource utilization monitoring tools are some
ways organizations can fix this. It's one of the most effective ways to manage budgets and deal with
major challenges in cloud computing.

10. Lack of expertise

Cloud computing is a highly competitive field, and there are many professionals who lack the required
skills and knowledge to work in the industry. There is also a huge gap in supply and demand for
certified individuals and many job vacancies.

Solution: Companies should retrain their existing IT staff and help them in upskilling their careers by
investing in Cloud training programs.

Unlock the Power of ITIL: Elevate Your ITIL Service Management. Discover the Key to
Streamlined Operations and Enhanced Customer Satisfaction. Learn More!

11. Control or Governance

Good IT governance ensures that the right tools are used, and assets get implemented according to
procedures and agreed-to policies. Lack of governance is a common problem, and companies use tools
that do not align with their vision. IT teams don't get total control of compliance, risk management,
and data quality checks, and there are many uncertainties faced when migrating to the Cloud from
traditional infrastructures.

Solution: Traditional IT processes should be adopted in ways to accommodate Cloud migrations.

12. Compliance

Cloud Service Providers (CSP) are not up-to-date when it comes to having the best data compliance
policies. Whenever a user transfers data from internal servers to the Cloud, they run into compliance
issues with state laws and regulations.

Solution: The General Data Protection Regulation (GDPR) Act is expected to expedite compliance
issues in the future for CSPs.

13. Multiple Cloud Management

Enterprises depend on multiple cloud environments due to scaling up and provisioning resources. One
of the hybrid cloud security challenges is that most companies follow a hybrid cloud strategy, and
many resort to multi-cloud. The problem is that infrastructures grow increasingly complex and
difficult to manage when multiple cloud providers get added, especially due to technological cloud
computing challenges and differences.

Solution: Creating strong data management and privacy policies is a starting point when it comes to
managing multi-cloud environments effectively.

14. Migration

Migration of data to the Cloud takes time, and not all organizations are prepared for it. Some report
increased downtimes during the process, face security issues, or have problems with data formatting
and conversions. Cloud migration projects can get expensive and are harder than anticipated.

Solution: Organizations will have to employ in-house professionals to handle their Cloud data
migration and increase their investments. Experts must analyze cloud computing issues and solutions
before investing in the latest platforms and services offered by CSPs.

15. Hybrid-Cloud Complexity

Hybrid-cloud complexity refers to cloud computing challenges arising from mixed computing,
storage, and services, and multi-cloud security causes various challenges. It comprises private cloud
services, public Clouds, and on-premises infrastructures, for example, products like Microsoft Azure
and Amazon Web Services - which are orchestrated on various platforms.

Solution: Using centralized Cloud management solutions, increasing automation, and hardening
security are good ways to mitigate hybrid-cloud complexity.

VIRTUALIZATON:

Virtualization is technology that you can use to create virtual representations of servers, storage,
networks, and other physical machines. Virtual software mimics the functions of physical hardware to run
multiple virtual machines simultaneously on a single physical machine.

3. Types of Virtualization

3.1. Full Virtualization

Red Hat Enterprise Linux contains virtualization packages and tools to run fully virtualized, unmodified,
operating system guests. This provides companies with the ability to consolidate older systems onto
newer, more efficient hardware, and reduces physical space and operating costs involved with powering
and cooling older, less efficient systems. Full virtualization offers lower I/O performance than native (or
bare-metal) installations of operating systems.

3.2. Para-Virtualization
Para-virtualization is a virtualization technique which involves running modified versions of operating
systems. The para-virtualized operating system is modified to be aware that it is being virtualized,
offering an increased ability for optimization as the guest is more aware of its environment. Performance
is generally very close to running bare-metal, non-virtualized operating systems.

3.3. Para-virtualized drivers

Para-virtualization and full virtualization can be combined to allow unmodified operating systems to
receive near native I/O performance by using para-virtualized drivers on fully virtualized operating
systems.

The para-virtualized drivers contain storage and network device drivers for fully virtualized Microsoft
Windows® guests. The drivers provide Microsoft Windows® guests running on Red Hat Enterprise
Linux with enhanced disk and network I/O performance.

load balancing:

Load balancing is the method that allows you to have a proper balance of the amount of work being done
on different pieces of device or hardware equipment. Typically, what happens is that the load of the
devices is balanced between different servers or between the CPU and hard drives in a single cloud
server.

Load balancing was introduced for various reasons. One of them is to improve the speed and performance
of each single device, and the other is to protect individual devices from hitting their limits by reducing
their performance.

Cloud load balancing is defined as dividing workload and computing properties in cloud computing. It
enables enterprises to manage workload demands or application demands by distributing resources among
multiple computers, networks or servers. Cloud load balancing involves managing the movement of
workload traffic and demands over the Internet.

Traffic on the Internet is growing rapidly, accounting for almost 100% of the current traffic annually.
Therefore, the workload on the servers is increasing so rapidly, leading to overloading of the servers,
mainly for the popular web servers. There are two primary solutions to overcome the problem of
overloading on the serve

Different Types of Load Balancing Algorithms in Cloud Computing:

1. Static Algorithm

Static algorithms are built for systems with very little variation in load. The entire traffic is divided
equally between the servers in the static algorithm. This algorithm requires in-depth knowledge of server
resources for better performance of the processor, which is determined at the beginning of the
implementation.

However, the decision of load shifting does not depend on the current state of the system. One of the
major drawbacks of static load balancing algorithm is that load balancing tasks work only after they have
been created. It could not be implemented on other devices for load balancing.

2. Dynamic Algorithm

The dynamic algorithm first finds the lightest server in the entire network and gives it priority for load
balancing. This requires real-time communication with the network which can help increase the system's
traffic. Here, the current state of the system is used to control the load.

The characteristic of dynamic algorithms is to make load transfer decisions in the current system state. In
this system, processes can move from a highly used machine to an underutilized machine in real time.

3. Round Robin Algorithm

As the name suggests, round robin load balancing algorithm uses round-robin method to assign jobs.
First, it randomly selects the first node and assigns tasks to other nodes in a round-robin manner. This is
one of the easiest methods of load balancing.

Processors assign each process circularly without defining any priority. It gives fast response in case of
uniform workload distribution among the processes. All processes have different loading times.
Therefore, some nodes may be heavily loaded, while others may remain under-utilised.
4. Weighted Round Robin Load Balancing Algorithm

Weighted Round Robin Load Balancing Algorithms have been developed to enhance the most
challenging issues of Round Robin Algorithms. In this algorithm, there are a specified set of weights and
functions, which are distributed according to the weight values.

Processors that have a higher capacity are given a higher value. Therefore, the highest loaded servers will
get more tasks. When the full load level is reached, the servers will receive stable traffic.

5. Opportunistic Load Balancing Algorithm

The opportunistic load balancing algorithm allows each node to be busy. It never considers the current
workload of each system. Regardless of the current workload on each node, OLB distributes all
unfinished tasks to these nodes.

The processing task will be executed slowly as an OLB, and it does not count the implementation time of
the node, which causes some bottlenecks even when some nodes are free.

6. Minimum To Minimum Load Balancing Algorithm

Under minimum to minimum load balancing algorithms, first of all, those tasks take minimum time to
complete. Among them, the minimum value is selected among all the functions. According to that
minimum time, the work on the machine is scheduled.

3. Round Robin Algorithm

As the name suggests, round robin load balancing algorithm uses round-robin method to assign jobs.
First, it randomly selects the first node and assigns tasks to other nodes in a round-robin manner. This is
one of the easiest methods of load balancing.

Processors assign each process circularly without defining any priority. It gives fast response in case of
uniform workload distribution among the processes. All processes have different loading times.
Therefore, some nodes may be heavily loaded, while others may remain under-utilised.

4. Weighted Round Robin Load Balancing Algorithm

Weighted Round Robin Load Balancing Algorithms have been developed to enhance the most
challenging issues of Round Robin Algorithms. In this algorithm, there are a specified set of weights and
functions, which are distributed according to the weight values.

Processors that have a higher capacity are given a higher value. Therefore, the highest loaded servers will
get more tasks. When the full load level is reached, the servers will receive stable traffic.

5. Opportunistic Load Balancing Algorithm

The opportunistic load balancing algorithm allows each node to be busy. It never considers the current
workload of each system. Regardless of the current workload on each node, OLB distributes all
unfinished tasks to these nodes.
The processing task will be executed slowly as an OLB, and it does not count the implementation time of
the node, which causes some bottlenecks even when some nodes are free.

6. Minimum To Minimum Load Balancing Algorithm

Under minimum to minimum load balancing algorithms, first of all, those tasks take minimum time to
complete. Among them, the minimum value is selected among all the functions. According to that
minimum time, the work on the machine is scheduled.

Scalability and Elasticity in Cloud Computing

Cloud Elasticity: Elasticity refers to the ability of a cloud to automatically expand or compress the
infrastructural resources on a sudden up and down in the requirement so that the workload can be
managed efficiently. This elasticity helps to minimize infrastructural costs. This is not applicable for all
kinds of environments, it is helpful to address only those scenarios where the resource requirements
fluctuate up and down suddenly for a specific time interval. It is not quite practical to use where
persistent resource infrastructure is required to handle the heavy workload.
The versatility is vital for mission basic or business basic applications where any split the difference in
the exhibition may prompts enormous business misfortune. Thus, flexibility comes into picture where
extra assets are provisioned for such application to meet the presentation prerequisites.
It works such a way that when number of client access expands, applications are naturally provisioned
the extra figuring, stockpiling and organization assets like central processor, Memory, Stockpiling or
transfer speed what’s more, when fewer clients are there it will naturally diminish those as
per prerequisite.
The Flexibility in cloud is a well-known highlight related with scale-out arrangements (level scaling),
which takes into consideration assets to be powerfully added or eliminated when required.
It is for the most part connected with public cloud assets which is generally highlighted in pay-per-use
or pay-more only as costs arise administrations.
The Flexibility is the capacity to develop or contract framework assets (like process, capacity or
organization) powerfully on a case by case basis to adjust to responsibility changes in the
applications in an autonomic way.
It makes make most extreme asset use which bring about reserve funds in foundation costs in general.
Relies upon the climate, flexibility is applied on assets in the framework that isn’t restricted to
equipment, programming, network, QoS and different arrangements.
The versatility is totally relying upon the climate as now and again it might become negative
characteristic where execution of certain applications probably ensured execution.
It is most commonly used in pay-per-use, public cloud services. Where IT managers are willing to pay
only for the duration to which they consumed the resources.
Example: Consider an online shopping site whose transaction workload increases during festive season
like Christmas. So for this specific period of time, the resources need a spike up. In order to handle this
kind of situation, we can go for a Cloud-Elasticity service rather than Cloud Scalability. As soon as the
season goes out, the deployed resources can then be requested for withdrawal.
Cloud Scalability: Cloud scalability is used to handle the growing workload where good performance
is also needed to work efficiently with software or applications. Scalability is commonly used where
the persistent deployment of resources is required to handle the workload statically.
Example: Consider you are the owner of a company whose database size was small in earlier days but
as time passed your business does grow and the size of your database also increases, so in this case you
just need to request your cloud service vendor to scale up your database capacity to handle a heavy
workload.
It is totally different from what you have read above in Cloud Elasticity. Scalability is used to fulfill the
static needs while elasticity is used to fulfill the dynamic need of the organization. Scalability is a
similar kind of service provided by the cloud where the customers have to pay-per-use. So, in
conclusion, we can say that Scalability is useful where the workload remains high and increases
statically.
Types of Scalability:
1. Vertical Scalability (Scale-up) –
In this type of scalability, we increase the power of existing resources in the working
environment in an upward direction.
2. 2. Horizontal Scalability: In this kind of scaling, the resources are added in a
horizontal row.
3. 3. Diagonal Scalability –
It is a mixture of both Horizontal and Vertical scalability where the resources are added
both vertically and horizontally.

Difference Between Cloud Elasticity and Scalability :

Cloud Elasticity Cloud Scalability

Elasticity is used just to meet the sudden up and Scalability is used to meet the static increase in
1 down in the workload for a small period of time. the workload.

Elasticity is used to meet dynamic changes,

Scalability is always used to address the increase
where the resources need can increase or
in workload in an organization.
2 decrease.

Elasticity is commonly used by small companies Scalability is used by giant companies whose
whose workload and demand increases only for a customer circle persistently grows in order to do
3 specific period of time. the operations efficiently.

It is a short term planning and adopted just to

Scalability is a long term planning and adopted
deal with an unexpected increase in demand or
just to deal with an expected increase in demand.
4 seasonal demands.

Replication:

What is Data Replication?

Data replication, as the term implies, is the creation of replicas/copies of data from one storage location to
another. This can be done between two on-premises appliances or between appliances in different
locations or to completely geo-physically separated appliances via cloud based services.
Replication in Cloud Computing refers to multiple storage of the same data to several different
locations by usually synchronization of these data sources. Replication in Cloud Computing is partly done
for backup and on the other hand to reduce response times, especially for reading data requests.

What are the benefits of data replication?

Improved reliability and disaster recovery

In case of an emergency, should your primary instance be compromised, it’s vital to have mission-critical
applications safeguarded with a replica that can be swapped in its place. Disaster recovery
replication methods work similarly to a backup generator; imagine blowing a critical fuse or your power grid
goes dark – you won’t have to worry because you have a backup generator to swoop in as a substitute and
keep your lights running.

Because replica instances are exact copies of primary instances, you can guarantee performance will not
falter, regardless of what happens to your primary. Even if the link between a primary and a replica breaks,
performance is still assured as the primary will enact a partial resynchronization, gathering the commands
that were not delivered to the replica during the disconnection. If not possible, a full resynchronization will be
initiated using a snapshot.

Increased app performance

By spreading the data across multiple instances, you’re helping to optimize read performance. Performance is
also optimized by having your data accessible in multiple locations, thus minimizing any latency issues. Also,
when replicas are directed to process most of your reads, that opens up space for your primary to tackle most
of the heavy lifting of writes.

More efficient IT teams

Reduction in IT labor to manually replicate data.

Understanding full data replication vs. partial replication

Full Database Replication occurs when an entire primary database is replicated within every replica instance
available. This is a holistic approach that mirrors pre-existing, new, and updated data to all destinations.
Though this approach is very comprehensive, it also calls for a considerable amount of processing power and
encumbers the network load because of the large size of the data being copied.

Unlike full replication, partial replication only mirrors some parts of the data, typically recently updated data.
Partial replication isolates particular bits of data following the importance of the data at a specific location.
For example, a large financial firm with headquarters in London could have many satellite offices operating
around the world, with an office in Boston, another in Kuala Lumpur, and so on.

Partial replication allows the analysts in London to have only UK-pertinent data at their site and have only
that data be consistently replicated for their needs. The other satellite offices in the United States and
Malaysia, respectively, can do the same and not bog down any one system, which improves performance and
minimizes network traffic.

Examples of data replication

Transactional replication

This form of database replication sees data from a primary database replicating data in real-time to a replica
instance by mirroring these changes in the order that they were made in the primary database. This optimizes
consistency. The replication takes what is called a “snapshot” of the data in the primary and uses that
snapshot as a blueprint of what needs to be replicated elsewhere. With transactional replication, you can track
and distribute changes as needed.

Snapshot replication

As its name suggests, snapshot replication takes a “snapshot” of the data from the primary as it appears at a
specific moment and moves it along to the replica. Like a photograph, snapshot replication captures what data
looks like at a point in time, as it looks when it moves from the primary to the replica, but doesn’t account for
how it is later updated. Thus, don’t use snapshot replication to make a backup.

In the event of a storage failure, snapshot replication will have no path to updated information. To keep your
information consistent, you can start with a snapshot, but then ensure that all changes made to the primary are
then passed on to every replica.

On the other hand, this method is rather helpful for recoveries in the event of accidental deletion. Think of it
like your Version History on Google Docs. Wish you could work on your presentation the way it looked four
hours ago? If Google Docs takes a snapshot of your work at hourly intervals, you could click back on that
version, or “snapshot,” from four hours ago and see what your information looked like then.

Merge replication

This method typically begins with a snapshot of the data and distributes that data to its replicas, and maintains
synchronization of data between the entire system. What makes merge replication different is that it allows
each node to make changes to the data independently but merges all those updates into a unified whole.

Merge replication also accounts for each change made at each node. To go back to our previous Google Docs
example, if you’ve ever shared a document with coworkers who then leave comments and edits on your
document, you’ll see who made what changes and at what time. Merge replication functions in a very similar
way.

Key-Based replication

Also known as key-based incremental data replication, this method leverages a replication key to identify,
locate and alter only the specific data that has been changed since the last update. By isolating that
information, it facilitates the backup process, working with only as much load as it has to. Though key-based
replication makes for a speedy method of refreshing new data, it comes with the disadvantage of failing to
replicate deleted data.

Monitoring:

Cloud monitoring comprises a series of strategies and practices for analyzing, tracking, and managing
cloud-based services and applications. As businesses scale their infrastructure and digital footprint, it
becomes vitally important for IT administrators and DevOps teams to maintain visibility into the
performance of their digital assets. Cloud monitoring provides an efficient way to achieve this visibility
while providing an enterprise with actionable insights to improve availability and user experiences.

Examples of monitoring metrics:

DEVICE TYPE METRIC

[Link] CPU-Usage,CPU-Idle

[Link] Memory-used,Memory free,Page-cache

[Link] Disk-usage,Bytes/sec(read/write),Operation/sec

[Link] Packets/sec(incoming/outgoing),Octets/sec(incoming/outgoing

Cloud Services and Platforms:

Compute Services: