What's changed: Initial version (topic 2.13, subtopics 2.13.1–2.13.4)
7.3System Architecture on Cloud Services
Learn how to architect systems on IaaS (Infrastructure as a Service): the difference between ephemeral storage and persistent storage, fixed IP vs floating IP, isolation via tenant networks, traffic control with firewalls and security groups, object storage, messaging systems/queues, and automatic node adjustment via an autoscaler.
Unlike an in-house data center, IaaS offers servers, storage, and networking as resources provisioned through an API. The HA and scalability ideas from earlier sections still apply, but understanding cloud-specific building blocks—ephemeral storage, tenant isolation, autoscalers—matters both in practice and on the exam.
7.3.1Storage and IP address types
- Ephemeral storage is tied to an instance's lifecycle: terminate the instance and the data disappears. Use it for things you can rebuild (the OS, caches). Persistent storage has a lifecycle independent of any instance (e.g., a block-storage volume) and survives instance termination—the right place for data you cannot afford to lose, like database files.
- Fixed IP is an IP address permanently assigned to an instance. Floating IP is an address reserved independently of any instance and reattached to whichever node needs it—reattaching it to a healthy node on failure achieves failover without changing the IP address clients use.
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.