Unit 16.assignment 1 Frontsheet
Unit 16.assignment 1 Frontsheet
Student declaration
I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism. I understand that
making a false declaration is a form of malpractice.
Grading grid
P1 P2 P3 P4 M1 M2 D1
Summative Feedback: Resubmission Feedback:
IV. THE SERVICE MODELS FOR CHOOSING AN ADEQUATE MODEL FOR A GIVEN
SCENARIO (P4).................................................................................................................................23
1. Compare 03 service models (IaaS, PaaS, SaaS)......................................................................................23
A. Definition.............................................................................................................................................23
B. Compare 03 service models (IaaS, PaaS, SaaS)..................................................................................24
2. Choose an adequate model for ATN app with justification...................................................................26
Table of Figures
Figure 1: History of cloud computing...........................................................................................................................5
Figure 2:Cloud computing...........................................................................................................................................6
Figure 3: The client-server model................................................................................................................................7
Figure 4: Peer-to-peer model......................................................................................................................................8
Figure 5: Deployment model.......................................................................................................................................9
Figure 6: SaaS............................................................................................................................................................10
Figure 7: PaaS............................................................................................................................................................11
Figure 8: IaaS.............................................................................................................................................................12
Figure 9: High performance computing.....................................................................................................................12
Figure 10: Characteristics of Cloud Computing..........................................................................................................14
Figure 11: Cloud computing in real life......................................................................................................................15
Figure 12: Cloud computing architecture diagram....................................................................................................18
Figure 13: Cloud deployment models........................................................................................................................19
Figure 14: Public cloud...............................................................................................................................................20
Figure 15: Private cloud.............................................................................................................................................21
Figure 16: Hybrid Cloud.............................................................................................................................................22
Figure 17: Community cloud......................................................................................................................................23
I. THE EVOLUTION AND FUNDAMENTAL CONCEPTS OF CLOUD
COMPUTING (P1)
1. The History of Cloud Computing
Before emerging the cloud computing, there was Client/Server computing which is
basically a centralized storage in which all the software applications, all the data and all the
controls are resided on the server side. If a single user wants to access specific data or run a
program, he/she need to connect to the server and then gain appropriate access, and then
he/she can do his/her business. Then after, distributed computing came into picture, where
all the computers are networked together and share their resources when needed. On the
basis of above computing, there was emerged of cloud computing concepts that later
implemented. (Javatpoint, 2022).
John MacCharty opined that computing may be marketed as a utility, much like water or
electricity, in a 1961 address at MIT. It was a fantastic idea, but like many great ideas, it
was ahead of its time. For the following few decades, even if the model was popular,
technology was simply not ready to support it. However, as time went on, technology
naturally adopted that concept, and a few years later, we remarked that:
Salesforce.com began offering users applications in 1999 using a straightforward
website. Enterprises received the programs via the Internet, making the dream of
computers as a utility a reality.
Amazon launched Amazon Web Services in 2002, offering solutions for computing,
storage, and even artificial intelligence. However, a fully commercial service that
was accessible to everyone didn't exist until the Elastic Compute Cloud was
introduced in 2006.
Google Apps began offering business cloud computing applications in 2009.
Of course, all the major firms have participated in the development of cloud computing,
some earlier than others. Microsoft introduced Windows Azure in 2009, and since then,
businesses like Oracle and HP have all joined the fray. This demonstrates that cloud
computing is now widely used.
A cloud can be either public or private. Anyone online can purchase services from a
public cloud. With specific access and authorization settings, a private cloud is a
proprietary network or data center that offers hosted services to a small group of users.
Cloud computing's objective, whether it's private or public, is to offer simple, scalable
access to computer resources and IT services.
The hardware and software elements necessary for a cloud computing model's correct
execution are included in cloud infrastructure. Another name for cloud computing is
utility computing or on-demand computing.
B. Client-server model
The client-server paradigm, a distributed application framework, splits the workload
between service providers, often known as servers, and clients, or the people who are
requesting the resource or service. A server receives a data request from a client
computer over the internet, processes it, and then transmits the requested data packets
back to the client. A client-server architecture is what this is. There isn't any client-to-
client resource sharing.
Email and the World Wide Web are a few examples of client-server models.
C. Peer-to-peer model
In its simplest form, a peer-to-peer (P2P) network is created when two or more PCs are
connected and share resources without going through a separate server computer. A
P2P network can be an ad hoc connection—a couple of computers connected via a
Universal Serial Bus to transfer files. A P2P network also can be a permanent
infrastructure that links a half-dozen computers in a small office over copper wires. Or
a P2P network can be a network on a much grander scale in which special protocols
and applications set up direct relationships among users over the Internet
(Computerworld, 2022).
Figure 4: Peer-to-peer model
E. Service Model
There are three different service models for cloud computing that each meet a certain
set of business requirements. Software as a Service (SaaS), Platform as a Service
(PaaS), and Infrastructure as a Service (IaaS) are the names of these three models.
SaaS: Software as a Service (SaaS) offers web-based solutions that are managed
by the software provider rather than by your company. This relieves your
business of the ongoing burden of managing software maintenance,
infrastructure, network security, data accessibility, and any other operational
issues related to program maintenance. User count, duration of use, data storage
capacity, and the volume of transactions are all factors that regularly affect SaaS
billing. This service model controls the highest market share in cloud
computing.
Figure 6: SaaS
Figure 7: PaaS
• File Storage Platform: A cloud application functions much like a website's file storage
platform. Several online file storage services give customers the option to save data,
documents, videos, and photos in the cloud. These tools offer customers a simple user
interface that they can use to access, browse, and upload documents from their local
computer to these websites. Both free and paid versions of these cloud computing services
are available. Customers that pay a monthly or annual membership fee can access premium
services.
Examples: Media Fire, Hot File, and Rapid Share are a few examples of online file storage
services.
• Meeting Applications: Virtual servers that enable on-site meeting rooms are included by
the majority of cloud computing providers. They offer meeting resources such as video
conferencing. These cloud computing applications allow users to begin virtual meetings.
Needs on a personal and professional level could push someone to start this. Users of the
services can quickly establish connections with others. To promote cooperation, they also
provide features for sharing presentations and screens.
Examples of popular cloud-based meeting applications include Zoom and Google
Meetings. Smooth video conferencing and cloud-based presentation services are available
from them.
• Management application: Project management software helps users take and instantly
share notes with multiple stakeholders. Since all stakeholders may consult the notes that
have been created and preserved in one location when assigning work, this aids in project
management. Both free and premium features are offered for these. The client can use the
premium features after paying a one-time subscription fee. These applications can be used
by users to meet their personal and professional needs.
Examples include management-related software like Evernote that are offered via the cloud
services.
• Antivirus Program: The cloud services also provide support and antivirus software. It
helps to improve the system's effective operation. Cloud antiviral software users can
routinely keep their systems clean. They give you the ability to identify and then get rid of
threats brought on by malware and various infestations. Due of their accessibility, these
features are beneficial to end users in a variety of ways. These applications are free to
download. They recognize the threat and alert the cloud's data center, which subsequently
helps end users resolve their issues.
II. APPROPRIATE ARCHITECTURAL CLOUD COMPUTING
FRAMEWORK FOR A GIVEN SCENARIO (P2)
1. Cloud Computing Architecture
The operational structure of a cloud computing system is defined by its architecture. It
includes the elements that interact with it as well as the dependencies on which it depends
for operation. The user layer, network layer, cloud management layer, and hardware
resource layer are the four layers of the cloud computing architecture that can be separated
based on how a user accesses the cloud.
We can provide a Cloud architecture example based on the image above.
(1) To begin with, users of cloud services are submitting requests to the cloud service.
(2) The automated scaling listener checks the cloud service in the following step to see if
the predetermined capacity threshold has been reached. There are two potential
outcomes in this situation.
Case 1: If the workload in this process does not go over the power threshold. In other
words, if the workload is below or equal to the capacity threshold, the cloud service will
process the request as usual. For instance, if the workload is 3 and the production threshold
is 4, a request to continue running will be issued to the cloud service.
Case 2: Nevertheless, there are more service requests coming from users of cloud services.
Workload is above acceptable performance level. Based on a predefined scaling policy, the
scaling listener automatically decides what to do next.
If the cloud service implementation is deemed eligible for further scaling, the scaling
listener would immediately begin the scaling process. The scaling listener would then send
the signal to the resource duplication system automatically, generating multiple copies of
the cloud service to satisfy the demands of the various customers.
The automatic listener continues to monitor, evaluate, and add IT resources as needed, even
while the workload has escalated. However, the user's request will be returned or
terminated if the cloud translation implementation is not eligible for further scaling.
For instance, the existing threshold is just 4 while the demand is increased to 6. Based on
the preset rate policy, the rate handler chooses the subsequent sequence of action
automatically. The sharing procedure will start if there are enough resources to scale the
deployment, such as enough RAM. In response to the quantity of user requests, the scale
listener then automatically sends a signal to the resource replication mechanism, creating
numerous instances of the cloud service. Now, the resource or some request will be routed
to the offered cloud service when the workload volume and the current threshold are
reached. However, requests from the user to the cloud service will be canceled if the
storage capacity does not match the scope of the deployment.
When you hear the terms "cloud" or "cloud computing," you probably image managed
computer resources. It's only one of a select few cloud deployment models, though. There
are other others. Typically, when we talk about the cloud, we mean the "public cloud." That
is one of the methods for deploying the cloud where every server is owned and managed by
the cloud service provider. Cloud hubs frequently contain tens of thousands of servers and
storage devices, enabling rapid loading. In many instances, choosing a certain region will
"closer" the info to the users. As a result, different cloud computing deployment patterns
are categorized based on where they are used. Let's first become familiar with the many
types so that we can choose which would best serve the requirements of your company.
A. Public Cloud
The public cloud deployment model is the most popular type of cloud. It's also the one
that springs to mind when the word "cloud" is mentioned. The primary concept behind
using a public cloud is that you don't own any hardware. You can use all the resources
thanks to a cloud service provider. Therefore, all that is needed to start using the public
cloud is to create an account. This idea defines "public" as a cloud that is accessible to
all users and whose resources are shared.
The key advantages of adopting the public cloud are scalability, effectiveness, and the
lack of a hardware requirement. Think about building a platform that can occasionally
support a heavy weight. If there were no cloud, you would have to give something up.
One strategy is to buy enough servers to handle the peak traffic. That would, however,
imply that all of those servers would typically be underutilized. The alternative would
be to buy merely the number of servers required to handle the normal traffic, but your
application would then operate poorly with irregular surges. With the public cloud, both
are feasible—enough capacity for load peaks without significant upfront costs.
Additionally, you can have load-based auto scaling and the ability to deliver resources
on-demand, and you only pay for the resources that you actually use. Cloud providers
offer a wide range of public cloud services in addition to simple virtual machines and
storage.
When you manage your data center in a manner similar to that of public cloud service
providers, a private cloud is created. You offer an abstraction layer over your actual
servers. Now you can move about with the flexibility of a public cloud. Additional
servers you add to your data center won't require configuration with a private cloud;
instead, they'll (semi)automatically join the cluster. You might be able to get a private
cloud from a public cloud provider. A cloud service provider will therefore separate
particular resources from the rest of the cloud and make them exclusively available to
you. But the fact remains that resources are allocated to a single business, whether you
acquire your private cloud from your data center or a cloud provider.
Several Private Cloud Computing Features:
Stricter security and privacy laws: Private clouds provide greater degrees of
security than public cloud services. Private clouds offer more superior security
services because of access limitations.
Greater Guaranteed Reliability: The virtualized operating style of a private
cloud suggests that the network is incredibly resilient to isolated disruptions and
recovers quickly.
Tighter control: Private cloud architecture and administration can be tailored to
a company's demands for a specific network solution because an organization
only has limited access to a resource pool.
Benefits of Private Cloud:
Data Privacy - It is perfect for keeping business data to which only authorized
individuals have access.
Security - Resource segmentation within the same infrastructure can aid in
better access and higher security levels.
Support for legacy systems that are unable to access the public cloud is provided
by this paradigm.
Limitations of Private Cloud:
Higher Cost - Considering the advantages you receive, your investment will
also be higher than with a public cloud. In this case, you'll have to pay for staff
training, software, hardware, and other resources.
Fixed Scalability: You can scale in a specific direction using the hardware you
select.
High Maintenance — Because it is handled internally, the maintenance
expenses also go up.
C. Hybird Cloud
As you might have guessed, a hybrid cloud deployment technique mixes a public and
private cloud. It is the second most common option because many businesses already
own equipment and wish to use it. An organization that utilizes both on-premises and
public cloud resources while connecting the two is said to be using a hybrid cloud. All
are supported by one system. It is possible to gradually migrate to the public cloud
using this very practical technique. Due to security or data protection regulations, some
firms are unable to operate solely in the public cloud; as a result, they may choose the
hybrid cloud to combine their requirements with the benefits of a public cloud. For
everything else, they use the public cloud, but they run sensitive data-heavy, mission-
critical software locally.
[Accessed 17 6 2022]
[Accessed 17 6 2022]
[Accessed 17 6 2022]
[Accessed 17 6 2022]