NOTE

Designing an Isolation System

A historical note on storage, service, and resource isolation, including Set deployment.

System DesignCreated Updated 1 min readhistorical

This is a historical learning note and may contain outdated or incomplete understanding.

1. What Is Isolation?

  • Split systems or resources apart so that when a failure occurs, its propagation range and impact range can be limited, avoiding a cascading failure.

2. How to Implement Isolation

2.1. Storage Isolation

  • For example, machines and databases are isolated between different microservices.

2.2. Service Isolation

  • In a multi-tenant model, a middle platform can isolate by APPID.

2.3. Resource Isolation Inside a Service

  • A caller invokes a callee. If the callee is unavailable, threads and similar resources need to be isolated so that all of the caller’s resources do not hang here.

3. Set Deployment

Set deployment means deploying services in standardized, normalized, and large-scale Set units according to business-function characteristics, thereby preventing failure propagation, operating massive services efficiently, and performing efficient capacity planning.

4. Isolation Component

Designing a Fault-Tolerance Component.md

5. References

Discussion

Sign in with GitHub to comment. Discussions are stored as GitHub Issues.View on GitHub