Term
|
Definition
| The ability to increase or decrease resources for any given workload |
|
|
Term
|
Definition
| add additional resources to service a workload |
|
|
Term
|
Definition
| add additional capabilities to manage an increase in demand to the existing resource |
|
|
Term
|
Definition
| The ability to automatically or dynamically increase or decrease resources as needed |
|
|
Term
|
Definition
| The ability to react quickly. Cloud services can allocate and deallocate resources quickly. |
|
|
Term
|
Definition
| The ability to remain up and running even in the event of a component or service no longer functioning. |
|
|
Term
|
Definition
| The ability to recover from an event which has taken down a cloud service. |
|
|
Term
|
Definition
| The ability reach audiences around the globe. |
|
|
Term
| Customer latency capabilities |
|
Definition
| If customers are experiencing slowness with a particular cloud service, they are said to be experiencing some latency. Even though modern fiber optics are fast, it can still take time for services to react to customer actions if the service is not local to the customer. Cloud services have the ability deploy resources in data centers around the globe, thus addressing customer latency issues. |
|
|
Term
| Predictive cost considerations |
|
Definition
| The ability for users to predict what costs they will incur for a particular cloud service. Costs for individual services are made available, and tools are provided to allow you predict what costs a service will incur. You can also perform analysis based on future growth. |
|
|
Term
| Technical skill requirements and considerations |
|
Definition
| Cloud services can provide and manage hardware and software for workloads. Therefore, getting a workload up and running with cloud services demands less technical resources than having IT teams build and maintain physical infrastructure for handling the same workload. A user can be expert in the application they want to run without having to need skills to build and maintain the underlying hardware and software infrastructure. |
|
|
Term
|
Definition
| Cloud providers offer a broad set of policies, technologies, controls, and expert technology skills that can provide better security than most organizations can otherwise achieve. The result is strengthened security, which helps to protect data, apps, and infrastructure from potential threats. |
|
|
Term
|
Definition
| ability to do things more cheaply and more efficiently when operating at a larger scale in comparison to operating at a smaller scale |
|
|
Term
|
Definition
| spending of money on physical infrastructure up front, and then deducting that expense from your tax bill over time. |
|
|
Term
|
Definition
| This is spending money on services or products now and being billed for them now. |
|
|
Term
|
Definition
| end users only pay for the resources that they use. Whatever they use is what they pay for. |
|
|
Term
| consumption-based model benefits |
|
Definition
No upfront costs
No need to purchase and manage costly infrastructure that they may or may not use to its fullest
The ability to pay for additional resources if and when they are needed
The ability to stop paying for resources that are no longer needed |
|
|
Term
| Public cloud characteristics |
|
Definition
-hardware owned by cloud provider.
-multiple organisations and users.
-does not require deep technical knowledge. |
|
|
Term
| Private cloud characteristics |
|
Definition
-owned and operated by the organisation using the resources.
-organisation responsible for operation of resources.
-owner and user of cloud services is the same.
-purchase maintenance and management
-operates in a single organization and used by single organization
-requires deep technical knowledge to setup. |
|
|
Term
| Hybrid cloud characteristics: |
|
Definition
-ownership is split
-specific resources run in private cloud and others run on public cloud.
-can still maintain the efficiencies and scalability of the public cloud |
|
|
Term
|
Definition
1. No CapEx: You don’t have to buy a new server in order to scale.
2. Agility: Applications can be made accessible quickly, and deprovisioned whenever needed.
3. Consumption-based model: Organizations pay only for what they use, and operate under an OpEx model.
4. Maintenance: Organizations have no responsibility for hardware maintenance or updates.
5. Skills: No deep technical skills are required to deploy, use, and gain the benefits of a public cloud. Organizations can leverage the skills and expertise of the cloud provider to ensure workloads are secure, safe, and highly available
6. |
|
|
Term
| Public Cloud Disadvantages: |
|
Definition
1. Security: There may be specific security requirements that cannot be met by using public cloud.
2. Compliance. There may be government policies, industry standards, or legal requirements which public clouds cannot meet.
3. Ownership: Organisations don't own the hardware or services and cannot manage them as they may wish.
4. Specific scenarios: If organizations have a unique business requirement, such as having to maintain a legacy application, it may be hard to meet that requirement with public cloud services. |
|
|
Term
| Private cloud Advantages: |
|
Definition
1. Control. Organizations have complete control over the resources.
2. Security. Organizations have complete control over security.
Compliance. If organizations have very strict security, compliance, or legal requirements, a private cloud may be the only viable option.
3. Specific scenarios. If an organisation has a specific scenario not easily supported by a public cloud provider (such as having to maintain a legacy application), it may be preferable to run the application locally. |
|
|
Term
|
Definition
1. Flexibility: The most flexible scenario; with a hybrid cloud setup, an organization can decide to run their applications either in a private cloud or in a public cloud.
2. Costs: Organizations can take advantage of economies of scale from public cloud providers for services and resources as they wish. This allows them to access cheaper storage than they can provide themselves.
3. Control: Organizations can still access resources over which they have total control.
4. Security: Organizations can still access resources for which they are responsible for security.
5. Compliance: organizations maintain the ability to comply with strict security, compliance, or legal requirements as needed.
6. Specific scenarios. Organizations maintain the ability to support specific scenarios not easily supported by a public cloud provider, such as running legacy applications. In this case, they can keep the old system running locally, and connect it to the public cloud for authorization or storage. Additionally, they could host a website in the public cloud, and link it to a highly secure database hosted in their private cloud. |
|
|
Term
| Disadvantages of Hybrid Cloud: |
|
Definition
Upfront CapEx. Upfront CapEx is still required before organizations can leverage a private cloud.
Costs. Purchasing and maintaining a private cloud to use alongside the public cloud can be more expensive than selecting a single deployment model.
Skills. Deep technical skills are still required to be able to set up a private cloud.
Ease of management. Organizations need to ensure there are clear guidelines to avoid confusion, complications or misuse. |
|
|
Term
|
Definition
1. Upfront cost: IaaS has no upfront costs. Users pay only for what they consume.
2. User ownership: The user is responsible for the purchase, installation, configuration, and management of their own software operating systems, middleware, and applications.
3. Cloud provider ownership: The cloud provider is responsible for ensuring that the underlying cloud infrastructure (such as virtual machines, storage and networking) is available for the user. |
|
|
Term
| shared responsibility model: |
|
Definition
| the cloud provider is responsible for ensuring the cloud infrastructure is functioning correctly; the cloud customer is responsible for ensuring the service they are using is configured correctly, is up to date, and is available to their customers. |
|
|
Term
|
Definition
Migrating workloads. Typically, IaaS facilities are managed in a similar way as on-premises infrastructure, and provide an easy migration path for moving existing applications to the cloud.
Test and development. Teams can quickly set up and dismantle test and development environments, bringing new applications to market faster. IaaS makes scaling development testing environments up and down fast and economical.
Website hosting. Running websites using IaaS can be less expensive than traditional web hosting.
Storage, backup, and recovery. Organizations avoid the capital outlay and complexity of storage management, which typically requires a skilled staff to manage data and meet legal and compliance requirements. IaaS is useful for managing unpredictable demand and steadily growing storage needs. It can also simplify the planning and management of backup and recovery systems. |
|
|
