Endpoints of ApsaraDB RDS for PostgreSQL instances - ApsaraDB RDS

ApsaraDB RDS for PostgreSQL provides the following types of endpoints to meet your business requirements: instance endpoint, database proxy endpoint, and Babelfish endpoint. This topic describes the endpoint types and the scenario of each endpoint type.

Description of endpoint types

Endpoint type	Description	Scenario
Instance endpoint	When you create an RDS instance, the system automatically generates an internal endpoint. The internal endpoint cannot be released. You can apply for or release a public endpoint. For more information, see Apply for or release a public endpoint. You can modify the internal and public endpoints and port numbers of your RDS instance. For more information, see View and change the endpoints and port numbers.	You want to connect to a single RDS instance.
Database proxy endpoint	The database proxy feature of ApsaraDB RDS for PostgreSQL provides the automatic read/write splitting capability. If the feature is enabled and a database proxy endpoint is used, ApsaraDB RDS for PostgreSQL automatically forwards write requests to the primary RDS instance and read requests to the corresponding read-only RDS instances. This way, the loads on the primary RDS instance are reduced. After the database proxy feature is enabled, a database proxy endpoint is provided by default. The Network Type parameter of the database proxy endpoint is fixed as Internal (VPC). You can create a database proxy endpoint for which the Network Type parameter is set to Public. For more information, see Manage database proxy endpoints. The database proxy endpoint and port number of the RDS instance can be modified. For more information, see Modify a database proxy endpoint and the port that is associated with the database proxy endpoint. Note For more information about database proxies, see What are database proxies?	You want to process a large number of read requests but a small number of write requests.
Babelfish endpoint	Babelfish is provided by ApsaraDB RDS for PostgreSQL and is developed based on the Babelfish for PostgreSQL open source project. You can enable Babelfish when you create an RDS instance. After you enable Babelfish for your RDS instance, your RDS instance can query and process data from both Microsoft SQL Server databases and PostgreSQL databases. You can also connect to the RDS instance over the Tabular Data Stream (TDS) port from an SQL Server client. By default, an internal endpoint is generated when you create an RDS instance and enable Babelfish for the RDS instance. The internal endpoint cannot be released. You can apply for or release a public endpoint. For more information, see Apply for or release a public endpoint. You can connect to the RDS instance for which Babelfish is enabled over the PostgreSQL port or TDS port for Babelfish from a PostgreSQL or SQL Server client. The internal and public endpoints and the TDS port for Babelfish can be modified. For more information, see View and change the endpoints and port numbers. Note For more information about Babelfish, see Introduction to Babelfish.	You want to use an RDS instance to process both SQL Server requests and PostgreSQL requests.