Skip to content
academia.sh

Course Beginner

Cloud Fundamentals

Published Updated

By the end of this course

Start course

01

The Cloud Concept

The definition of renting and its limit: measuring on-demand resources and elasticity, which decision each of the infrastructure, platform, and software service models hands over, the cost and control difference between public, private, and hybrid deployment, comparing the fixed and variable cost structure against an on-premises installation, and drawing the responsibility boundary between provider and customer item by item.

  1. 01 What Is Cloud Computing The measure of on-demand resources: in the same 120-day demand curve, the time from capacity request to use dropping from 30 days to 1 day, unmet requests under the peak-forming load falling from 84,689 to 1,260 and the days capacity ran short dropping from 15 to 2, idle capacity falling from 764 to 254 unit-days, while under a flat load the requests saved stay at zero, and the eight items that remain at exit dropping to four.
  2. 02 Service Models The measure of infrastructure, platform, and software service: in a set of 26 decisions, decisions handed over climbing from 5 to 23 and 25, the yearly touches on kept decisions dropping from 91 to 82, 19, and 4, the share of handovers recoverable via a parameter falling from 40% to 39% and 12%, 6, 5, 4, and 1 of six requirement requests being met, and the carried-over decision share at exit dropping from 100% to 92%, 69%, and 35%.
  3. 03 Deployment Models The measure of public, private, and hybrid deployment: in the same six-component workload, the public layout failing to place two components and six of seven call links failing to be established, control items kept running 8/24, 36/36, 20/36, and 28/36, fixed reserved capacity at 0%, 100%, 45%, and 75%, the elasticity window at 1.0, 21.0, 10.0, and 16.0 days, and hybrid paying 18 operating items, two identity directories, and six mapping items in both of its forms.
  4. 04 Comparison with On-Premises The measure of capital expense against operating expense: in the same 36-month usage curve, the break-even month landing at 15, 19, and 13 under the visible total, and at 36, past the window, and 23 under the full total, the items hidden under own hardware holding 64%, 55%, and 48% of the total, and 13% under renting, and the winner shifting as the exit month moves from 12 to 36 — from renting to own hardware in the flat curve, and back to renting in the peak-forming curve. Costs are fictional and are written in a fictional unit.
  5. 05 Shared Responsibility Model The measure of the boundary between provider and customer: in a 24-item responsibility matrix, items passing to the provider climbing from 6 to 16 and 20, items falling in the gap at 2, 4, and 5, overlapping items at 2, 4, and 2, eight incidents closing in a total of 56, 73, and 68 rounds, with 28, 35, and 35 of those rounds coming from the gap alone, 4, 5, and 4 of eight incidents closing with data loss, and carried-over items at exit dropping from 18 to 8 and 4.

02

Infrastructure Geography and Design Principles

Where the rented capacity sits and how it is priced: separating the region from the availability zone as a failure domain, edge locations for proximity to the user, how the pillars of the design framework constrain one another, the price-and-risk balance of on-demand, reserved, and spot capacity, and the cost of the rehost, replatform, and refactor migration strategies.

  1. 01 Regions and Availability Zones Counting where the rented item physically sits: the item a single-zone placement leaves standing after a zone loss, the extra capacity cost of spreading across two and three zones, how a region loss stays independent of zone spread, and the time cross-region latency adds to the nightly batch job.
  2. 02 Edge Locations Counting proximity to the user together with its cost: how average distance and latency fall as edge locations are added, where the gain per location stops, the share of work types the edge cannot serve, and the daily count of stale responses returned from the edge.
  3. 03 The Pillars of the Design Framework Scoring a decision set across five pillars and counting the tension between pillars: how many decisions raise one pillar while lowering another, which pillar pair is most tense, deriving the pillar no decision improves, and comparing the pillar profile of handed-over decisions against what remains and the share that does not carry at exit.
  4. 04 Pricing Models Running on-demand, reserved, and spot capacity against the same load profile: total cost, work re-run because of reclaimed capacity, unused commitment, the gap between list price and effective unit price, and the liability left when exiting mid-window.
  5. 05 Cloud Migration Strategies Comparing rehost, replatform, and refactor across the same ten-item set: the decision handed over, migration days, the provider-specific item that makes exit harder, the wave count and how long the two systems run together, the annual load of the item left behind, and the cost of a dual system that never ends.

Final exam

Cloud Fundamentals — Final Exam

In preparation

This course's question bank is not complete yet. The exam opens here automatically once enough questions are added.

Start typing to search.

↑↓ ↵ Esc navigate · open · close