Skip to content

Commit fcfafe8

Browse files
committed
new guides
1 parent 8755679 commit fcfafe8

9 files changed

+4
-6
lines changed

articles/postgresql/flexible-server/concepts-connection-pooling-best-practices.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,11 +9,11 @@ author: rayi
99
ms.date: 08/30/2023
1010
---
1111

12-
# CONNECTION POOLING STRATEGY FOR POSTGRESQL USING PGBOUNCER
12+
# Connection Pooling Strategy for PostgreSQL Using PgBouncer
1313

1414
[!INCLUDE [applies-to-postgresql-flexible-server](../includes/applies-to-postgresql-flexible-server.md)]
1515

16-
Strategic guidance for selecting connection pooling mechanism for PostgreSQL
16+
Strategic guidance for selecting connection pooling mechanism for PostgreSQL.
1717

1818
## Introduction
1919

@@ -39,8 +39,6 @@ The effective utilization of PgBouncer can be categorized into three distinct us
3939
1. Application independent centralized PgBouncer deployments
4040
1. Inbuilt PgBouncer and Database deployment
4141

42-
:::image type="content" source="./media/concepts-connection-pooling-best-practices/design-patterns.png" alt-text="Diagram for App co-location":::
43-
4442

4543
Each of these patterns has its own advantages & disadvantages.
4644

@@ -142,7 +140,7 @@ By utilizing **PgBouncer** as a separate service, you can efficiently manage and
142140

143141
[**PgBouncer** sidecar proxy image](https://hub.docker.com/_/microsoft-azure-oss-db-tools-pgbouncer-sidecar) published in Microsoft container registry can be used to create and deploy a service.
144142

145-
:::image type="content" source="./media/concepts-connection-pooling-best-practices/centralized-aks.png" alt-text="Diagram for PGBouncer as a service within AKS":::
143+
:::image type="content" source="./media/concepts-connection-pooling-best-practices/centralized-aks.png" alt-text="Diagram for PgBouncer as a service within AKS":::
146144

147145
Some of the key benefits & limitations of this deployment method are:
148146

@@ -164,7 +162,7 @@ While **PgBouncer** running as a standalone service offers benefits such as cent
164162

165163
Azure Database for PostgreSQL – Flexible Server offers [PgBouncer](https://github.com/pgbouncer/pgbouncer) as a built-in connection pooling solution. This is offered as an optional service that can be enabled on a per-database server basis. PgBouncer runs in the same virtual machine as the Postgres database server. As the number of connections increases beyond a few hundreds or thousand, Postgres may encounter resource limitations. In such cases, built-in PgBouncer can provide a significant advantage by improving the management of idle and short-lived connections at the database server.
166164

167-
Refer link to enable and set up PgBouncer connection pooling in Azure DB for PostgreSQL Flexible server
165+
Refer link to enable and set up PgBouncer connection pooling in Azure DB for PostgreSQL Flexible server.
168166

169167
Some of the key benefits & limitations of this deployment method are:
170168

Loading
Loading
Loading
93.4 KB
Loading
-21.7 KB
Loading
-118 KB
Loading
5.75 KB
Loading
-35.8 KB
Loading

0 commit comments

Comments
 (0)