0% found this document useful (0 votes)
32 views

Unit2 CloudArchitecture Notes

unit 2 for AIML diploma students

Uploaded by

dhanashree
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
32 views

Unit2 CloudArchitecture Notes

unit 2 for AIML diploma students

Uploaded by

dhanashree
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

Unit2: Cloud Architecture and Cloud Service Management(12 Marks)

Cloud Computing Architecture:-

Front End:
The client uses the front end, which contains a client-side interface and
application. Both of these components are important to access the Cloud
computing platform. The front end includes web servers (Chrome,
Firefox, Opera, etc.), clients, and mobile devices.
Frontend of the cloud architecture refers to the client side of cloud
computing system. Means it contains all the user interfaces and
applications which are used by the client to access the cloud computing
services/resources. For example, use of a web browser to access the cloud
platform.
i. Client Infrastructure – Client Infrastructure is a part of the frontend
component. It contains the applications and user interfaces which
are required to access the cloud platform.
ii. In other words, it provides a GUI( Graphical User Interface ) to
interact with the cloud.

Back End: The back end is used by the service provider. It manages all
the resources that are required to provide cloud computing services. It includes
a huge amount of data storage, security mechanism, virtual machines, deploying
models, servers, traffic control mechanisms, etc.

Backend refers to the cloud itself which is used by the service provider. It
contains the resources as well as manages the resources and provides security
mechanisms. Along with this, it includes huge storage, virtual applications,
virtual machines, traffic control mechanisms, deployment models, etc.

1.Application – Application in backend refers to a software or platform to


which client accesses. Means it provides the service in backend as per the client
requirement.

2. Service – Service in backend refers to the major three types of cloud based
services like SaaS, PaaS and IaaS. Also manages which type of service the user
accesses.

Service is an essential component in cloud architecture

Its responsibility is to provide utility in the architecture

In a Cloud, few widely used services among the end-users are storage
application development environments and web services

3. Runtime Cloud- Runtime cloud in backend provides the execution and


Runtime platform/environment to the Virtual machine.

4. Storage – Storage in backend provides flexible and scalable storage service


and management of stored data. It stores and maintains data like files, videos,
documents, etc. over the internet

Some of the popular examples of storage services are below:

Oracle Cloud-Storage

Microsoft Azure Storage

Its capacity varies depending upon the service providers available in the market

5. Infrastructure – Cloud Infrastructure in backend refers to the hardware and


software components of cloud like it includes servers, storage, network devices,
virtualization software etc.

6. Management – Management in backend refers to management of backend


components like application, service, runtime cloud, storage, infrastructure, and
other security mechanisms etc. Its task is to allot specific resources to a specific
task, it simultaneously performs various functions of the cloud environment

It helps in the management of components like application, task, service,


security, data storage, and cloud infrastructure
In simple terms, it establishes coordination among the cloud resources

7. Security – Security in backend refers to implementation of different security


mechanisms in the backend for secure cloud resources, systems, files, and
infrastructure to end-users. Security is an integral part of back-end cloud
infrastructure

It provides secure cloud resources, systems, files, and infrastructure to end-users

Also, it implements security management to the cloud server with virtual


firewalls which results in preventing data loss

8. Internet – Internet connection acts as the medium or a bridge between


frontend and backend and establishes the interaction and communication
between frontend and backend.

 Benefits of Cloud Computing Architecture:-


The cloud computing architecture is designed in such a way that:
 It solves latency issues and improves data processing requirements
 It reduces IT operating costs and gives good accessibility to access data
and digital tools
 It helps businesses to easily scale up and scale down their cloud resources
 It has a flexibility feature which gives businesses a competitive advantage
 It results in better disaster recovery and provides high security
 It automatically updates its services
 It encourages remote working and promotes team collaboration
 Cloud Computing Architecture Components
i. Some of the important components of Cloud Computing
architecture that we will be looking into are as follows:
ii. Hypervisor
iii. Management Software
iv. Deployment Software
v. Network
vi. Cloud Server
vii. Cloud Storage

 Hypervisor:-
a. It is a virtual machine monitor which provides Virtual Operating
Platforms to every user
b. It also manages guest operating systems in the cloud
c. It runs a separate virtual machine on the back end which consists of
software and hardware
d. Its main objective is to divide and allocate resources
 Management Software:-
a. Its responsibility is to manage and monitor cloud operations with
various strategies to increase the performance of the cloud
b. Some of the operations performed by the management software
are:
c. compliance auditing
d. management of overseeing disaster
e. contingency plans
 Deployment Software:-
a. It consists of all the mandatory installations and configurations
required to run a cloud service
b. Every deployment of cloud services are performed using a
deployment software
c. The three different models which can be deployed are the
following:
d. SaaS - Software as a service hosts and manages applications of the
end-user.
e. PaaS - Platform as a service helps developers to build, create, and
manage applications.
f. IaaS - Infrastructure as a service provides services on a pay-as-you-
go pricing model.
 Network
a. It connects the front-end and back-end. Also, allows every user to
access cloud resources
b. It helps users to connect and customize the route and protocol
c. It is a virtual server which is hosted on the cloud computing
platform
d. It is highly flexible, secure, and cost-effective
 Cloud Storage
a. Here, every bit of data is stored and accessed by a user from
anywhere over the internet
b. It is scalable at run-time and is automatically accessed
c. Data can be modified and retrieved from cloud storage over the
web
 ADVANTAGES OF CLOUD ARCHITECTURE
a. Cloud architecture uses simple APIs to provide easily accessible
services to the user through the internet medium.
b. It provides scale on demand feature to increase the industrial
strength.
c. It provides the transparency between the machines so that users
don’t have to worry about their data. Users can just perform the
functionality without even knowing the complex logic's
implemented in cloud architecture.
 DISADVANTAGES OF CLOUD ARCHITECTURE
a. We put our data in the hands of a third party. Then how about
security, privacy, confidentiality, contingency recovery? This has
to be checked carefully. What we have today are cloud providers
who comply with all the regulations, laws, restrictions, etc.

Cloud Service Models:-


 There are the following three types of cloud service models -
Infrastructure as a Service (IaaS)
Platform as a Service (PaaS)
Software as a Service (SaaS)

i. 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 –
1. Resources are available as a service
2. Services are highly scalable
3. Dynamic and flexible
4. GUI and API-based access
5. Automated administrative tasks
Example: DigitalOcean, Linode, Amazon Web Services
(AWS), Microsoft Azure, Google Compute Engine (GCE),
Rackspace, and Cisco Metacloud.
ii. 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 –
1. Accessible to various users via the same development
application.
2. Integrates with web services and databases.
3. Builds on virtualization technology, so resources can easily
be scaled up or down as per the organization's need.
4. Support multiple languages and frameworks.
5. Provides an ability to "Auto-scale".
Example: AWS Elastic Beanstalk, Windows Azure, Heroku,
Force.com, Google App Engine, Apache Stratos, Magento
Commerce Cloud, and OpenShift.
iii. 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 –
1. Managed from a central location
2. Hosted on a remote server
3. Accessible over the internet
4. Users are not responsible for hardware and software updates.
Updates are applied automatically.
5. The services are purchased on the pay-as-per-use basis
Example: BigCommerce, Google Apps, Salesforce,
Dropbox, ZenDesk, Cisco WebEx, ZenDesk, Slack, and
GoToMeeting.
 Difference between IaaS, PaaS, and SaaS:-

IaaS Paas SaaS

It provides a virtual data center to It provides virtual platforms and It provides web software and
store information and create tools to create, test, and deploy apps to complete business
platforms for app development, apps. tasks.
testing, and deployment.

It provides access to resources It provides runtime It provides software as a


such as virtual machines, virtual environments and deployment service to the end-users.
storage, etc. tools for applications.

It is used by network architects. It is used by developers. It is used by end users.

IaaS provides only Infrastructure. PaaS provides SaaS provides


Infrastructure+Platform. Infrastructure+Platform
+Software.

 Continuous delivery using PaaS:-


1. PaaS came from the desire of developers to be provided with a pre-
defined service layer that may consist of multiple tiers (Application
Server, Database, Messaging Systems, etc.) and sits upon a
platform that is provisioned using an automated IaaS platform like
OpenStack.
2. OpenShift Online provides you a free service where you can try a
PaaS platform. But how does this 1:1 mapping between a
developer and the development environment help inside an
enterprise enterprise environment, that consists of multiple
developers working in teams. With these teams working on
different components of a distributed application.
3. Take a look at the following picture shows a typical Continuous
Delivery Lifecycle that consists of 3 different development teams
on the left. Each Team (A,B,C) develop on their own feature
branch. That branch is tied to an OpenShift gear. When the
developer issues a git push, the code is pushed to the remote
repository.
4. Each push triggers a jenkins build in a centralized jenkins instance.
You can integrate with an existing jenkins instance as well.

Cloud Deployment Models:-


It works as your virtual computing environment with a choice of
deployment model depending on how much data you want to store and
who has access to the Infrastructure.
 Different Types Of Cloud Computing Deployment Models:-
Deployment models for cloud computing are categorized based on their
location. To know which model would best fit the requirements of your
organization, let us first learn about the various types.

Public Cloud:-
The name says it all. It is accessible to the public. Public
deployment models in the cloud are perfect for organizations with
growing and fluctuating demands. It also makes a great choice for
companies with low-security concerns. It is also a great delivery
model for the teams with development and testing. Its
configuration and deployment are quick and easy, making it an
ideal choice for test environments.

Benefits of Public Cloud:-


o Minimal Investment - As a pay-per-use service, there is no
large upfront cost and is ideal for businesses who need quick
access to resources
o No Hardware Setup - The cloud service providers fully fund
the entire Infrastructure
o No Infrastructure Management - This does not require an in-
house team to utilize the public cloud.

Limitations of Public Cloud:-

o Data Security and Privacy Concerns - Since it is accessible


to all, it does not fully protect against cyber-attacks and
could lead to vulnerabilities.
o Reliability Issues - Since the same server network is open to
a wide range of users, it can lead to malfunction and outages
o Service/License Limitation - While there are many resources
you can exchange with tenants, there is a usage cap.

Private Cloud:-

The private cloud offers bigger opportunities that help meet


specific organizations' requirements when it comes to
customization. It's also a wise choice for mission-critical
processes that may have frequently changing requirements.
Benefits of Private Cloud:-
o Data Privacy - It is ideal for storing corporate data where
only authorized personnel gets access
o Security - Segmentation of resources within the same
Infrastructure can help with better access and higher
levels of security.
o Supports Legacy Systems - This model supports legacy
systems that cannot access the public cloud.

Limitations of Private Cloud:-


o Higher Cost - With the benefits you get, the investment
will also be larger than the public cloud. Here, you will
pay for software, hardware, and resources for staff and
training.
o Fixed Scalability - The hardware you choose will
accordingly help you scale in a certain direction
o High Maintenance - Since it is managed in-house, the
maintenance costs also increase.

Community Cloud:-

The community cloud operates in a way that is similar to the


public cloud. There's just one difference - it allows access to
only a specific set of users who share common objectives and
use cases. This type of deployment model of cloud computing is
managed and hosted internally or by a third-party vendor.
However, you can also choose a combination of all three.
Benefits of Community Cloud:-

o Smaller Investment - A community cloud is much cheaper than the


private & public cloud and provides great performance

o Setup Benefits - The protocols and configuration of a community cloud


must align with industry standards, allowing customers to work much
more efficiently.

Limitations of Community Cloud:-

o Shared Resources - Due to restricted bandwidth and storage capacity,


community resources often pose challenges.
o Not as Popular - Since this is a recently introduced model, it is not that
popular or available across industries

Hybrid Cloud:-

As the name suggests, a hybrid cloud is a combination of two or more cloud


architectures. While each model in the hybrid cloud functions differently, it is
all part of the same architecture. Further, as part of this deployment of the cloud
computing model, the internal or external providers can offer resources
Benefits of Hybrid Cloud:-

Cost-Effectiveness - The overall cost of a hybrid solution decreases since it


majorly uses the public cloud to store data.

Security - Since data is properly segmented, the chances of data theft from
attackers are significantly reduced.

Flexibility - With higher levels of flexibility, businesses can create custom


solutions that fit their exact requirements

Limitations of Hybrid Cloud:-

Complexity - It is complex setting up a hybrid cloud since it needs to integrate


two or more cloud architectures

Specific Use Case - This model makes more sense for organizations that have
multiple use cases or need to separate critical and sensitive data

A Comparative Analysis of Cloud Deployment Models:-


Important Factors Public Private Community Hybrid
to Consider

Setup and ease of Easy Requires Requires Requires professional IT


use professional IT professional IT Team
Team Team

Data Security and Low High Very High High


Privacy

Scalability and High High Fixed requirements High


flexibility

Cost-Effectiveness Most Most expensive Cost is distributed Cheaper than private but
affordable among members more expensive than
public

Reliability Low High Higher High

Cloud Service Management:-


i. Service level agreements in Cloud computing:-
A Service Level Agreement (SLA) is the bond for performance
negotiated between the cloud services provider and the client.
Earlier, in cloud computing all Service Level Agreements were
negotiated between a client and the service consumer. Service level
agreements are also defined at different levels which are mentioned
below:
o Customer-based SLA
o Service-based SLA
o Multilevel SLA
Few Service Level Agreements are enforceable as contracts,
but mostly are agreements or contracts which are more along
the lines of an Operating Level Agreement (OLA) and may
not have the restriction of law. It is fine to have an attorney
review the documents before making a major agreement to
the cloud service provider. Service Level Agreements
usually specify some parameters which are mentioned
below:
Availability of the Service (uptime)
Latency or the response time
Service components reliability
Each party accountability
Warranties
In any case, if a cloud service provider fails to meet the
stated targets of minimums then the provider has to pay the
penalty to the cloud service consumer as per the agreement.
So, Service Level Agreements are like insurance policies in
which the corporation has to pay as per the agreements if any
casualty occurs.

 Advantages of SLA :-
Improved communication: A better framework for
communication between the service provider and the client is
established through SLAs, which explicitly outline the degree of
service that a customer may anticipate. This can make sure that
everyone is talking about the same things when it comes to
service expectations.
Increased accountability: SLAs give customers a way to hold
service providers accountable if their services fall short of the
agreed-upon standard. They also hold service providers
responsible for delivering a specific level of service.
Better alignment with business goals: SLAs make sure that
the service being given is in line with the goals of the client by
laying down the performance goals and service level
requirements that the service provider must satisfy.
Reduced downtime: SLAs can help to limit the effects of
service disruptions by creating explicit protocols for issue
management and resolution.
Better cost management: By specifying the level of service
that the customer can anticipate and providing a way to track
and evaluate performance, SLAs can help to limit costs. Making
sure the consumer is getting the best value for their money can
be made easier by doing this.
Disadvantages of SLA:-
Complexity: SLAs can be complex to create and maintain, and
may require significant resources to implement and enforce.
Rigidity: SLAs can be rigid and may not be flexible enough to
accommodate changing business needs or service requirements.
Limited service options: SLAs can limit the service options
available to the customer, as the service provider may only be
able to offer the specific services outlined in the agreement.
Misaligned incentives: SLAs may misalign incentives between
the service provider and the customer, as the provider may focus
on meeting the agreed-upon service levels rather than on
providing the best service possible.
Limited liability: SLAs are not legal binding contracts and
often limited the liability of the service provider in case of
service failure.
 Service level objectives (SLOs):-
Service level objectives (SLOs) are measurable goals that define what
constitutes good service for a cloud service over a given period of time.
SLOs are built on three types of information:
Service level indicators (SLIs): Measure the service's performance
Performance goals: Specify the desired level of performance
Compliance period: A time period for measuring how the SLI compares
to the performance goal
SLOs can be used to track end-to-end customer experience. For example,
an SLO might specify that latency can exceed 300 milliseconds in only
5% of requests over a 30-day period, or that a system must have 99%
availability over a calendar week.
SLO monitoring tools can help you set up alerting policies based on SLO
performance. This can help you align your business needs with
engineering reliability goals, and make trade-offs between product
development and operational work.

 Policies and mechanisms for Service Management:-


A policy typically refers to the principal guiding decisions, whereas
mechanisms represent the means to implement policies. Separation of
policies from mechanisms is a guiding principle in computer science.
Cloud resource management policies can be loosely grouped into five
classes:
1. Admission control.
2. Capacity allocation.
3. Load balancing.
4. Energy optimization.
5. Quality-of-service (QoS) guarantees
The explicit goal of an admission control policy is to prevent the system
from accepting workloads in violation of high-level system policies.
Capacity allocation means to allocate resources for individual instances;
an instance is an activation of a service. Load balancing and energy
optimization can be done locally, but global load-balancing and energy
optimization policies encounter the same difficulties. Load balancing and
energy optimization are correlated and affect the cost of providing the
services Quality of service is that aspect of resource management that is
probably the most difficult to address and, at the same time, possibly the
most critical to the future of cloud computing.

You might also like