GCP Cloud Storage & Filestore

Cloud Storage (object storage)

What it is

Global object storage (not a POSIX filesystem). Buckets → objects (prefix가 “폴더처럼” 보일 뿐).
Exabyte scale, ms TTFB, high availability across classes, single API (JSON/XML + gcloud storage).

Key model

Buckets: globally unique name, no nesting.
Objects: inherit bucket’s storage class by default; size min 0, practically unlimited (quota 내).
Access via gcloud storage, JSON/XML APIs.

Storage classes & locations

Location types

Region (e.g., london) — lowest latency if compute is co-located.
Dual-region (e.g., fi-nl) — paired, geo-redundant, good perf + higher availability.
Multi-region (e.g., us) — geo-redundant, best for global content.

Classes (모두 11 9s durability = data won’t be lost; availability는 클래스별 차이)

Class	Access pattern	Min duration	Retrieval $	Typical use
Standard	Hot / frequent	None	None	websites, streaming, mobile/gaming, analytics near compute
Nearline	≤ monthly	30d	Low	backups, long-tail media, archives with occasional reads
Coldline	≤ quarterly	90d	Higher	DR, colder archives
Archive	< yearly	365d	Highest	long-term archive; ms access (not hours/days)

Changing classes (bucket vs object)

Upload 시 bucket default class 적용; per-object class override 가능.
Bucket location type(region ↔ dual/multi)는 나중에 변경 불가(새 버킷 필요).
비용 최적화: 드물게 쓰는 object만 Nearline/Coldline/Archive로 변경.