× close
About Us
Home   /   About Us   /   Study   /   The "cloud" that everyone is discussing, do you really understand cloud computing?
2023/07/04

The "cloud" that everyone is discussing, do you really understand cloud computing?

The "cloud" that everyone is discussing, do you really understand cloud computing?

 

Definition of Cloud Computing: Various types of terminal devices can provide users (individuals or organizations) with shared software/hardware computing resources (servers, databases, customer service systems, CRM, analytical reports, artificial intelligence, etc.) through the internet (cloud). Cloud computing is usually based on virtualization technology and provides resources and services quickly according to the customer's needs (charging based on usage). This is different from the current mainstream on-premise solutions in Taiwan: all computing resources and related service equipment are self-responsible, with certain distinctions. Of course, depending on the nature or scale of different projects, Nanxun will recommend suitable solutions tailored to the situation. However, the following provides a rough distinction between cloud solutions and on-premise solutions.

 

 

Cloud computing, according to the "National Institute of Standards and Technology (NIST) definition," can be divided into three deployment models:

 

Public Cloud: Public cloud services provide software/hardware computing resources to customers through the internet and third-party service providers. It is like taking a bus where resources like the driver, seats, and air conditioning are shared. The payment model for consumers is based on what services they use and for how long, offering great flexibility and cost-effectiveness.

Although it is a public cloud, it does not mean that the user data stored in the cloud is accessible to anyone. Public cloud providers implement strict access control mechanisms for users. Nanxun has financial clients, for example, who comply with all regulatory requirements from the Financial Supervisory Commission and use the Genesys Cloud omnichannel intelligent customer service provided by Amazon Web Services' public cloud.

 

Private Cloud: A private cloud is like buying your own car. All resources on this car are exclusively owned by a single entity (organization or individual), and the payment model usually involves an upfront investment. Using private cloud services reduces dependence on network bandwidth limitations and regulatory concerns. Additionally, private cloud services provide greater control over the cloud infrastructure, related data, and applications.

 

Hybrid Cloud: Hybrid cloud is like renting a car, combining the advantages of both public cloud (taking a bus) and private cloud (owning a car). In a hybrid cloud model, users typically process non-critical information in the public cloud but maintain control over critical services and data in the private cloud.

 

Now, let's understand the three service models of cloud computing:

 

 

Infrastructure as a Service (IaaS): IaaS provides virtualized computing resources, such as servers, storage, and networks, over the internet. Users can manage and control the operating systems, storage, and deployed applications while leaving the underlying infrastructure to the service provider.

 

Platform as a Service (PaaS): PaaS offers a platform and development environment for users to build, deploy, and manage applications. Users can focus on application development, while the service provider takes care of the underlying infrastructure, operating systems, and runtime environments.

 

Software as a Service (SaaS): SaaS delivers software applications over the internet on a subscription basis. Users can access and use these applications through a web browser or API without the need for local installation or maintenance. The service provider handles the entire infrastructure, platform, and application management.

 

These deployment models and service models provide different options for organizations and individuals to leverage cloud computing based on their specific needs and requirements.

 

 

Infrastructure as a Service (IaaS) - Typically used by SysAdmins (system administrators)

 

Consumers use "basic computing resources" such as VM (virtual machines), network components, and storage space. Consumers have control over operating systems, middleware, storage, data, and applications. Examples of IaaS providers include AWS EC2 and Microsoft Azure.

 

Platform as a Service (PaaS) - Typically used by Developers

 

Consumers use the platform for developing, testing, deploying, and managing applications. Consumers have control over the application's operating environment (and partial control over the hosting), but they do not have control over the underlying network infrastructure, operating systems, and hardware. Examples of PaaS providers include Google App Engine and AWS EBS.

 

Software as a Service (SaaS) - Typically used by End Customers

 

Consumers use software applications but do not have control over the software development, operating systems, or hardware. Software service providers offer services to customers through a subscription-based model, and customers can directly access the service through a web browser. Examples of SaaS services include Gmail, Microsoft Office 365, Salesforce, and Nanxun Genesys Cloud omnichannel customer service.

 

To explain the differences between these three cloud service models in a more relatable way, let's use a food analogy. Let's say today I want to eat a mille-feuille cake (a layered pastry dessert). If I choose a completely on-premise solution, I would be responsible for every step of making the mille-feuille cake, including having my own kitchen equipment, utilities, ingredients, and baking. However, if I choose the IaaS service model, I would outsource certain aspects of the kitchen preparation, such as utilities and kitchen equipment, to a service provider, but I would still handle ingredient preparation and baking myself. If I opt for PaaS, I would also outsource the ingredient preparation to the service provider, and I would only be responsible for baking (software development). Finally, if I choose the SaaS service model, it's like going to a restaurant to eat the mille-feuille cake or ordering it for delivery. I don't have to worry about any backend preparation details; I can simply enjoy the final product (the developed software).