Unit2 CloudArchitecture Notes
Unit2 CloudArchitecture Notes
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.
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.
In a Cloud, few widely used services among the end-users are storage
application development environments and web services
Oracle Cloud-Storage
Its capacity varies depending upon the service providers available in the market
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.
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.
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.
Private Cloud:-
Community Cloud:-
Hybrid Cloud:-
Security - Since data is properly segmented, the chances of data theft from
attackers are significantly reduced.
Specific Use Case - This model makes more sense for organizations that have
multiple use cases or need to separate critical and sensitive data
Cost-Effectiveness Most Most expensive Cost is distributed Cheaper than private but
affordable among members more expensive than
public
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.