Document Center

All Products

Document Center

Platform For AI:Overview of invocation methods

Last Updated:Aug 21, 2025

EAS provides five service invocation methods. You can choose the method that best suits your requirements.

Architecture overview

Important

After you configure a virtual private cloud (VPC), vSwitch, and security group for an EAS service, the following conditions apply:

Accessing EAS through a shared gateway or a dedicated gateway is not restricted by security group rules. You can set access rules for a dedicated gateway using a whitelist.
Accessing EAS through NLB, Nacos, or a VPC direct connection, and all outbound traffic from EAS, are restricted by security group rules.

Feature comparison

Invocation method	Features and scenarios
Shared gateway	Low cost. Does not support custom access policies. Provides insufficient isolation and elasticity. Suitable for services with low traffic that do not have high requirements for performance and isolation.
Dedicated gateway	Supports custom access policies, cross-VPC and cross-cloud access, and custom domain names. Suitable for services with high traffic that require high security, stability, and performance.
VPC direct connection	Access services through an IP address without a gateway. This improves access performance and reduces latency, but provides weak load balancing capabilities. Suitable for services with high traffic.
Server Load Balancer (NLB)	Requires a separately provisioned NLB. This lets you fully use the access control capabilities of NLB. Suitable for services with very high traffic that require load balancing capabilities.
Service discovery (Nacos)	Requires a separately provisioned Nacos instance. This lets you fully use the access control capabilities of Nacos. Suitable for scenarios where services are registered using Nacos.