클라우드 과정(MTC AZ-900) - 7주차

< (클라우드)컴퓨팅의 진화 >

Dedicated -> VMs -> Containers -> Functions

• A Physical server wholly utilized by a single customer.
• You have to guess your capacity, you'll overpay for an underutilized server.
• Upgrading beyond your capacity will be slow and expensive.
• You are limited by your Operating System.
• Multiple apps can result in conflicts in resource sharing.
• You have a guarantee of security, privacy and full uility of underlying resource.

Dedicated -> VMs -> Containers -> Functions

• You can multiple Virtual Machines on one machine.
• Hypervisor is the software layer that lets you the VMs.
• A physical server shared by multiple customers.
• You are pay for a fraction of the server.
• You'll overpay for an underutilized Virtual Machine.
• You are limited by your Guest Operating System.
• Multiple apps on a single Virtual Machine can result in conflicts in resource sharing.

Dedicated -> VMs -> Containers -> Functions

• Virtual Machine running multiple containers.
• Docker Deamon is the name of the software layer that lets you run multiple containers.
• You can maximum the utilize the avilable capacity which is more cost-effective.
• Your containers share the same underlying OS so containers are more efficient than multiple VMs.
• Multiple apps can run side by side without being limited to the same OS requirements and will not caught conflicts during resource sharing.

Dedicated -> VMs -> Containers -> Functions

• A managed VMs running managed containers.
• Known as Serverless Compute.
• You upload a piece of code choose the amount of memory and duration.
• Only responsible for code and data, nothing else.
• Very cost-effective, only pay for the time code is running, VMs run when there is code to be executed.
• Cold Starts is a side-effect of this setup.(컴퓨터를 키자마자 바로 동작x)

---

Geographies : 데이터 센터의 지리적 위치

• Discrete markets that preserve data residency and compliance boundaries.
• Allow customers with specific data-residency(데이터 레지던시) and compliance(규정준수) needs to keep their data and applications in close proximity.
  - 데이터 레지던시 규제 : 의료, 금융, 공공 등의 산업에서 고객 및 개인정보 데이터를 특정 지역(국내)에서 벗어날 수 없도록 하는 것 ==> 프라이빗 클라우드, 하이브리드 클라우드

---

Regions : 지구상에서 지리적으로 가까운 지역, 대기 시간이 짧고 지연 시간이 짧은 네트워크와 네트워크로 연결된 하나 이상의 여러 데이터 센터를 포함, 각 지역 내의 resource를 지능적으로 할당 및 제어하여 작업 부하가 적절히 균형을 유지.

• Provides flexibility and scale.
• Preserves data residency.
• Select regions close to your users.

-> BCDR를 위해 Regions 사용

 

BCDR(Business Continuity and Disaster Recovery, 무중단 업무 및 재해 복구) : Azure 쌍을 이루는 지역

• 지역 쌍은 동일한 지리 내의 두 지역으로 구성.
• Azure는 지역 쌍에서 플랫폼 업데이트(계획된 유지 관리)를 직렬화하여 각 쌍의 한 지역이 한 번에 업데이트.
• 중단이 여러 지역에 영향을 주는 경우 각 쌍에서 하나 이상의 지역이 복구를 위해 우선 순위가 지정.
• Each Azure region is paired with another region.
• In an outage(정전), recoverey of one region is prioritized out of every pair.
• Azure system updates are rolled out to paired regions sequentially (not at the same time).

 

Define Availability sets(무중단 서비스 제공을 위함)

1. Update domains (UD) : Scheduled maintenance, performance or security updates are sequenced through update domains.

2. Fault domains (FD) : Provide a physical separation of workloads acress different hardware in a datacenter.

 

Define Availability zones (가용성 영역, UD, FD로 이뤄진 Availability zone을 여러 개 묶어 하나의 Region으로 만든 것)

• Physically separate locations within an Azure region.
• Includes one or more datacenters, equipped with independent power, cooling, and networking.
• If one availability zone goes down, the other continuses working.