Differences and performance gaps between cross-zone HA file gateways and Basic Edition file gateways-Cloud Storage Gateway(CSG)-阿里云帮助中心

This topic compares cross-zone high availability (HA) file gateways and Basic Edition file gateways across four dimensions: architecture, usage, bandwidth, and latency, to help you choose the appropriate gateway type based on your business scenario.

Differences between cross-zone HA file gateways and Basic Edition file gateways

	Cross-zone HA file gateway	Basic Edition file gateway
Usage	You must configure a virtual mount IP address before you can mount and use the gateway. The virtual mount IP address can be changed after the gateway is created.	The mount IP address is automatically assigned by the system and cannot be changed.
Usage	Shares are deployed on different nodes. When you create a share, you can bind it to a different virtual mount IP address.	Shares are created on the instance node. All shares are bound to the same assigned mount IP address.
Architecture	Contains two service nodes deployed in different availability zones. The gateway remains operational when a single node or a single availability zone fails.	A single service node deployed in one availability zone. An availability zone failure may pose availability risks.
Instance read/write bandwidth limit	Cross-zone HA file gateways deploy shares on two nodes, so the overall read bandwidth limit of the instance is twice that of a Basic Edition file gateway. The write bandwidth limit is the same as that of a Basic Edition gateway.
Instance read/write latency	Cross-zone HA file gateways use synchronous replication for cross-zone data replication. Write request latency is affected by inter-zone network latency and is slightly higher than that of a Basic Edition file gateway. Read request latency is not affected.

How to choose a gateway type

Scenarios for choosing a cross-zone HA file gateway:

Your business has zero tolerance for availability zone-level failures, such as production workloads or cluster shared storage.
You need higher read throughput. The dual-node architecture doubles the overall read bandwidth limit compared to the Basic Edition.
Your business can accept slightly increased write latency in exchange for availability zone-level fault tolerance.

Scenarios for choosing a Basic Edition file gateway:

Your business can tolerate brief unavailability during an availability zone failure, such as development and testing environments or non-critical data processing pipelines.
You have strict write latency requirements and cannot accept the additional latency caused by cross-zone synchronous replication.
You prefer simpler mount configuration. Basic Edition gateways automatically assign mount IP addresses, with no virtual IP management required.