# connection pool

A connection pool maintains reusable database connections so applications or threads can obtain and return them as needed.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Gartner Analyst: "Your Next Database User Won't Be a Person"

DevFeed: [Gartner Analyst: "Your Next Database User Won't Be a Person"](<https://devfeed.tech/articles/gartner-analyst-your-next-database-user-won-t-be-a-person-137751.md>)

Original publisher: [Read original article](<https://flashdba.com/2026/11/16/gartner-analyst-your-next-database-user-wont-be-a-person/>)

Author: flashdba

Published: 2026-11-16T17:27:25Z

Content type: opinion

Language: en

Sources: [Flashdba](<https://devfeed.tech/sources/flashdba.md>)

Topics: [Database](<https://devfeed.tech/topics/database.md>), [cloud cost management](<https://devfeed.tech/topics/cloud-cost-management.md>), [database-scalability](<https://devfeed.tech/topics/database-scalability.md>), [read-replica](<https://devfeed.tech/topics/read-replica.md>), [database monitoring](<https://devfeed.tech/topics/database-monitoring.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [after](<https://devfeed.tech/tags/after.md>), [age-of-ai](<https://devfeed.tech/tags/age-of-ai.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [alarm](<https://devfeed.tech/tags/alarm.md>), [budget](<https://devfeed.tech/tags/budget.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [database](<https://devfeed.tech/tags/database.md>), [databases](<https://devfeed.tech/tags/databases.md>), [databases-and-agentic-ai](<https://devfeed.tech/tags/databases-and-agentic-ai.md>), [first](<https://devfeed.tech/tags/first.md>), [gartner](<https://devfeed.tech/tags/gartner.md>), [governance](<https://devfeed.tech/tags/governance.md>), [inferencing](<https://devfeed.tech/tags/inferencing.md>), [next](<https://devfeed.tech/tags/next.md>), [operational](<https://devfeed.tech/tags/operational.md>), [performance](<https://devfeed.tech/tags/performance.md>), [user](<https://devfeed.tech/tags/user.md>)

### AI overview

The excerpt argues that gradual AI agent adoption is more likely to expose budget and governance problems before cloud operational databases fail. Much agent activity is read-heavy, and cloud platforms can absorb added load with replicas, serverless compute, or higher provisioned limits; this can keep queries and latency healthy while shifting the strain into infrastructure costs, often charged to teams that did not deploy the agents. Database failure can still occur beyond elasticity limits, but the article says organizations may pay for the approach well before that point. Governance is a separate, pre-existing gap: an agent using a service account may be identifiable only as that account, leaving records without attribution to the agent, its initiator, authority, or purpose. Higher volume multiplies these gaps without necessarily triggering an alert. The excerpt also notes that database choices are moving from central DBA teams to product and engineering leads as DBA headcount declines, while system owners may still receive the bill and audit findings.

### Source excerpt

A Gartner analyst asked what AI agents would break first. On cloud operational databases the budget breaks before the database - and governance already has.

## How to Build Multi-Tenant SaaS in Symfony Without Sacrificing Database Isolation

DevFeed: [How to Build Multi-Tenant SaaS in Symfony Without Sacrificing Database Isolation](<https://devfeed.tech/articles/how-to-build-multi-tenant-saas-in-symfony-without-sacrificing-database-isolation-135517.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-to-build-multi-tenant-saas-in-symfony-without-sacrificing-database-isolation?source=rss>)

Author: MattLeads

Published: 2026-11-16T04:40:39Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Per-user Database](<https://devfeed.tech/topics/per-user-database.md>), [Symfony](<https://devfeed.tech/topics/symfony.md>), [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [Database](<https://devfeed.tech/topics/database.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [cache](<https://devfeed.tech/tags/cache.md>), [database](<https://devfeed.tech/tags/database.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [free](<https://devfeed.tech/tags/free.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [messenger](<https://devfeed.tech/tags/messenger.md>), [multi-tenant](<https://devfeed.tech/tags/multi-tenant.md>), [multitenancy](<https://devfeed.tech/tags/multitenancy.md>), [php](<https://devfeed.tech/tags/php.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [redis](<https://devfeed.tech/tags/redis.md>), [saas](<https://devfeed.tech/tags/saas.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [symfony](<https://devfeed.tech/tags/symfony.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>), [workers](<https://devfeed.tech/tags/workers.md>)

### AI overview

The article's approach keeps a separate PostgreSQL database for each tenant while serving free tenants from shared Symfony processes; paying tenants can remain on dedicated deployments. A request path prefix sets the tenant, and a DBAL connection wrapper selects its database at query time, reconnecting on tenant switches and rejecting switches inside a transaction. A cache decorator namespaces tenant data, with tag-aware pools requiring tenant-prefixed tags. A custom Messenger transport polls each placed tenant's Redis stream, rotates tenants for fairness, and stamps messages from their stream; worker listeners set tenant context before retries or failures are stored and clear it afterward. An optional in-flight cap limits each tenant's concurrent jobs, though a worker crash can leave a slot occupied for up to three minutes. Placement is read from Redis, and migrations run in separate tenant-configured processes. The demo reports about 6.27 ms per database switch on a laptop; the article says this may matter for high-volume workers. It advises against the design when cross-tenant atomic transactions are needed, a tenant merits its own deployment, or services retain tenant-specific,

### Source excerpt

Run free tenants of a database-per-tenant Symfony 8.1 app on one shared deployment, with the DB connection, cache and Messenger workers following the tenant.

## Improve RDS Proxy multiplexing for PostgreSQL, Part 1: Common causes

DevFeed: [Improve RDS Proxy multiplexing for PostgreSQL, Part 1: Common causes](<https://devfeed.tech/articles/improve-rds-proxy-multiplexing-for-postgresql-part-1-common-causes-133437.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/improve-rds-proxy-multiplexing-for-postgresql-part-1-common-causes/>)

Author: Pavel Rabinovich

Published: 2026-11-13T21:08:09Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [fragmentation](<https://devfeed.tech/tags/fragmentation.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [multiplexing](<https://devfeed.tech/tags/multiplexing.md>), [pool](<https://devfeed.tech/tags/pool.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [rds](<https://devfeed.tech/tags/rds.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [transactions](<https://devfeed.tech/tags/transactions.md>)

### AI overview

RDS Proxy multiplexing for PostgreSQL is reduced when sessions are pinned, client identities fragment the pool, or transactions remain open. CloudWatch indicators help distinguish them: elevated session-pinned connections suggest pinning; many backend connections with low borrowing and pinning can indicate fragmentation; sustained borrowing and open transactions point to transactions held too long. Fixes include upgrading the PostgreSQL JDBC driver to 42.7.x or newer, removing application SET statements, setting Spark JDBC writes to isolationLevel=NONE, and using InitQuery for shared session defaults. Standardize username, database, and ApplicationName among clients that should share a pool, while preserving separate users when privilege or audit needs require them. Commit promptly or enable autocommit where explicit transaction control is unnecessary. PostgreSQL targets do not support the proxy's SET pinning filter, and CloudWatch gauges can miss short-lived borrow cycles.

### Source excerpt

RDS Proxy multiplexes many client connections across a small pool of database connections, but connection pinning, pool fragmentation, and uncommitted transactions can silently disable that benefit for PostgreSQL workloads. Part 1 shows how to recognize each condition with Amazon CloudWatch metrics and the fix that restores multiplexing.

## Break your dependencies on purpose: introducing Quarkus Resiliency Testing

DevFeed: [Break your dependencies on purpose: introducing Quarkus Resiliency Testing](<https://devfeed.tech/articles/break-your-dependencies-on-purpose-introducing-quarkus-resiliency-testing-135957.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-resiliency-testing/>)

Author: Georgios Andrianakis (https://twitter.com/geoand86)

Published: 2026-11-12T00:00:00Z

Content type: tutorial

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [Chaos Engineering](<https://devfeed.tech/topics/chaos-engineering.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>)

Tags: [client](<https://devfeed.tech/tags/client.md>), [clients](<https://devfeed.tech/tags/clients.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [database](<https://devfeed.tech/tags/database.md>), [docker](<https://devfeed.tech/tags/docker.md>), [examples](<https://devfeed.tech/tags/examples.md>), [exception](<https://devfeed.tech/tags/exception.md>), [exceptions](<https://devfeed.tech/tags/exceptions.md>), [extension](<https://devfeed.tech/tags/extension.md>), [failure](<https://devfeed.tech/tags/failure.md>), [fallback](<https://devfeed.tech/tags/fallback.md>), [fault-injection](<https://devfeed.tech/tags/fault-injection.md>), [inventory](<https://devfeed.tech/tags/inventory.md>), [junit](<https://devfeed.tech/tags/junit.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [resiliency](<https://devfeed.tech/tags/resiliency.md>), [retries](<https://devfeed.tech/tags/retries.md>), [services](<https://devfeed.tech/tags/services.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

Quarkus Resiliency Testing injects network and resource failures into `@QuarkusTest` runs so real clients and application configuration face hangs, broken responses, and unavailable dependencies. `NetworkFaultsProfile` routes supported outbound connections through in-process proxies; tests can check bounded waits and recovery, bulkheads, payment retries with stable idempotency keys, JDBC timeouts and pool exhaustion, stale connections, transaction rollback, and Kafka publishing behavior. The examples show that retries, timeouts, exception mapping, and transaction choices determine customer-visible outcomes; fault injection alone does not provide resilience. The article also describes disk-full and DNS faults, Dev UI exploration, and an outbox alternative when orders must be accepted during Kafka outages. Requirements include Quarkus 4 and Java 21. Limits include plaintext HTTP/1.x for HTTP faults, Linux-only `connectTimeout()`, and no `@QuarkusIntegrationTest` support; some Dev Services still require Docker.

### Source excerpt

Imagine a customer placing an order. Your service reserves stock, charges their card, and stores the result. On a normal day, each step takes milliseconds and the customer sees a confirmation. Now imagine inventory accepts the connection but never answers. Or the payment provider charges the card just before the connection breaks. Or the database stops responding while your application is holding a connection from its pool. These failures demand different responses. Waiting longer can use up your workers; retrying can charge the customer twice; catching an exception does nothing if the client never throws one. A happy-path test tells you little about any of them. Quarkus Resiliency Testing lets you reproduce these conditions in a @QuarkusTest, using your application's real clients and configuration. Let's follow that order through four failure scenarios and turn each one into a test. The examples are excerpts from the resilient-orders sample, which includes the endpoints, supporting classes and complete tests. Put the failure on the wire Add the test dependency: <dependency> <groupId>io.quarkiverse.resiliencytesting</groupId> <artifactId>quarkus-resiliency-testing-junit</artifactId> <version>0.6.0</version> <scope>test</scope> </dependency> With NetworkFaultsProfile, the extension discovers supported outbound connections from Quarkus configuration, including Dev Services, and redirects them through proxies inside the test JVM. The proxy normally relays traffic. During a fault, the real client encounters the broken connection and reacts with its own timeouts, retries and exceptions. A mock that throws an exception can check a fallback; this also exercises the client configuration that determines whether, and when, that fallback is reached. The fault injection needs no separate container or sidecar; dependencies such as the sample's PostgreSQL Dev Service can still need Docker. 1. Inventory stops answering The customer clicks "Place order", but inventory never respond

## Diagnose Amazon Aurora MySQL performance using CloudWatch Database Insights

DevFeed: [Diagnose Amazon Aurora MySQL performance using CloudWatch Database Insights](<https://devfeed.tech/articles/diagnose-amazon-aurora-mysql-performance-using-cloudwatch-database-insights-129583.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/diagnose-amazon-aurora-mysql-performance-using-cloudwatch-database-insights/>)

Author: Aayushi Mittal

Published: 2026-11-11T16:46:38Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [MySQL](<https://devfeed.tech/topics/mysql.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [database monitoring](<https://devfeed.tech/topics/database-monitoring.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [table-partitioning](<https://devfeed.tech/topics/table-partitioning.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [database](<https://devfeed.tech/tags/database.md>), [diagnose](<https://devfeed.tech/tags/diagnose.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [mysql-performance](<https://devfeed.tech/tags/mysql-performance.md>), [performance](<https://devfeed.tech/tags/performance.md>)

### AI overview

CloudWatch Database Insights represents database activity as average active sessions (DB load), plots it against Max vCPU, and breaks it down by wait event and top SQL. Sustained load above capacity suggests queuing, though lock waits can stall work even below that line. The article recommends tracing dominant waits to correlated SQL before changing the system: tune CPU-heavy queries; use EXPLAIN and indexes for table reads; batch Aurora redo-log writes; reduce hot-key contention and transaction length for SYNCH waits; use connection pooling for connection churn; and limit or paginate results when client-return waits dominate. Scaling or Aurora replicas are options when CPU remains the bottleneck after tuning. Standard mode provides per-instance views and seven days of history; Advanced mode adds fleet monitoring and past-period analysis, with additional cost. Fleet triage ranks instances by load before drilling into waits and SQL.

### Source excerpt

When an Aurora MySQL or Amazon RDS for MySQL database slows down, it can be hard to tell why. This post shows how to read DB load in Amazon CloudWatch Database Insights, interpret the most common MySQL wait events, and turn each into a concrete action, so you can fix the real bottleneck instead of scaling up to a larger instance.

## Database Sharding Clearly Explained

DevFeed: [Database Sharding Clearly Explained](<https://devfeed.tech/articles/database-sharding-clearly-explained-121476.md>)

Original publisher: [Read original article](<https://blog.levelupcoding.com/p/database-sharding-clearly-explained>)

Author: Nikki Siapno

Published: 2026-11-06T15:03:19Z

Content type: article

Language: en

Sources: [Level Up Coding System Design Newsletter](<https://devfeed.tech/sources/level-up-coding-system-design-newsletter.md>)

Topics: [sharding](<https://devfeed.tech/topics/sharding.md>), [database-scalability](<https://devfeed.tech/topics/database-scalability.md>), [table-partitioning](<https://devfeed.tech/topics/table-partitioning.md>), [read-replica](<https://devfeed.tech/topics/read-replica.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [Memcached](<https://devfeed.tech/topics/memcached.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-engineering](<https://devfeed.tech/tags/ai-engineering.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [application](<https://devfeed.tech/tags/application.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [automate](<https://devfeed.tech/tags/automate.md>), [automation](<https://devfeed.tech/tags/automation.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [cache](<https://devfeed.tech/tags/cache.md>), [caching](<https://devfeed.tech/tags/caching.md>), [connection-pooling](<https://devfeed.tech/tags/connection-pooling.md>), [consistent-hashing](<https://devfeed.tech/tags/consistent-hashing.md>), [constraint](<https://devfeed.tech/tags/constraint.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [data](<https://devfeed.tech/tags/data.md>), [data-movement](<https://devfeed.tech/tags/data-movement.md>), [database](<https://devfeed.tech/tags/database.md>), [sharding](<https://devfeed.tech/tags/sharding.md>)

### AI overview

Sharding splits data across multiple database servers to distribute storage and workload when one server remains a constraint after simpler measures such as query optimization, caching, vertical scaling, read replicas, and partitioning. Horizontal sharding divides rows while keeping the same schema; vertical sharding separates tables or workloads. The key design challenge is choosing a shard key that spreads both data and traffic evenly. Queries and transactions spanning shards require coordination and add latency and complexity, while changing shard counts can require difficult data movement. The text recommends keeping common operations within one shard, planning for rebalancing, monitoring shards individually, automating maintenance, and testing realistic workloads. Sharding can extend scalability, but replaces a single-server bottleneck with distributed-system and operational challenges.

### Source excerpt

The hardest part of sharding isn't splitting the data.

## How to fix "too many connections" in PostgreSQL (step-by-step guide)

DevFeed: [How to fix "too many connections" in PostgreSQL (step-by-step guide)](<https://devfeed.tech/articles/how-to-fix-too-many-connections-in-postgresql-step-by-step-guide-92746.md>)

Original publisher: [Read original article](<https://www.red-gate.com/simple-talk/databases/postgresql/how-to-fix-too-many-connections-in-postgresql-step-by-step-guide/>)

Author: Achyut Tripathi

Published: 2026-10-21T12:00:00Z

Content type: tutorial

Language: en

Sources: [Simple Talk](<https://devfeed.tech/sources/simple-talk.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [Learning](<https://devfeed.tech/topics/learning.md>)

Tags: [connection-pooling](<https://devfeed.tech/tags/connection-pooling.md>), [database](<https://devfeed.tech/tags/database.md>), [database-administration](<https://devfeed.tech/tags/database-administration.md>), [databases](<https://devfeed.tech/tags/databases.md>), [featured](<https://devfeed.tech/tags/featured.md>), [guide](<https://devfeed.tech/tags/guide.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [sql](<https://devfeed.tech/tags/sql.md>)

### AI overview

PostgreSQL returns a "too many connections" error when open sessions reach `max_connections`; the article lists per-request connection creation, connections left open after programs terminate, long-lived idle sessions, misconfigured pools, and traffic spikes as possible causes. It demonstrates the limit with a local test: after lowering `max_connections` to 20, a Python script attempts 30 connections and later closes the successful ones. Suggested responses are to close connections properly, reuse a finite set through pooling, inspect idle sessions with `pg_stat_activity` before terminating them, and monitor session counts regularly. Raising `max_connections` may allow more sessions but uses more resources and can mask underlying connection management problems.

### Source excerpt

Getting PostgreSQL's "too many connections" error? Learn what causes it, how to reproduce it safely, and 5 proven fixes -- including connection pooling and monitoring with pg_stat_activity.... The post How to fix "too many connections" in PostgreSQL (step-by-step guide) appeared first on Simple Talk.

## Your Client Connection Pool isn't the Problem

DevFeed: [Your Client Connection Pool isn't the Problem](<https://devfeed.tech/articles/your-client-connection-pool-isn-t-the-problem-90286.md>)

Original publisher: [Read original article](<https://www.yugabyte.com/blog/client-connection-pool/>)

Author: Manav Kumar

Published: 2026-10-19T11:12:56Z

Content type: article

Language: en

Sources: [The Distributed SQL Blog](<https://devfeed.tech/sources/the-distributed-sql-blog.md>)

Topics: [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [Service fabric](<https://devfeed.tech/topics/service-fabric.md>)

Tags: [connection-manager](<https://devfeed.tech/tags/connection-manager.md>), [connection-pool](<https://devfeed.tech/tags/connection-pool.md>), [database](<https://devfeed.tech/tags/database.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [ysql](<https://devfeed.tech/tags/ysql.md>), [yugabyte](<https://devfeed.tech/tags/yugabyte.md>), [yugabytedb](<https://devfeed.tech/tags/yugabytedb.md>)

### AI overview

The article describes how a customer addressed peak database connection demand from autoscaling Kubernetes services using YugabyteDB YSQL Connection Manager. It explains how the manager multiplexes many logical client connections over fewer physical database backends, allowing the customer to keep existing application pool settings and cluster hardware. The article notes that workload ratios vary and that long transactions or sticky session features can reduce multiplexing.

### Source excerpt

A customer faced 1,920 required connections against a cluster sized for 360 days before go-live. More hardware or smaller pools was not the solution. Discover how YSQL Connection Manager resolved the issue with a single setting and no application changes. The post Your Client Connection Pool isn't the Problem appeared first on Yugabyte.

## YSQL Connection Manager is Now GA

DevFeed: [YSQL Connection Manager is Now GA](<https://devfeed.tech/articles/ysql-connection-manager-is-now-ga-87140.md>)

Original publisher: [Read original article](<https://www.yugabyte.com/blog/ysql-connection-manager-is-now-ga/>)

Author: Suranjan Kumar

Published: 2026-10-14T10:18:44Z

Content type: release

Language: en

Sources: [The Distributed SQL Blog](<https://devfeed.tech/sources/the-distributed-sql-blog.md>)

Topics: [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [Distributed Systems & Parallel Computing](<https://devfeed.tech/topics/distributed-systems-parallel-computing.md>)

Tags: [connection-manager](<https://devfeed.tech/tags/connection-manager.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [release-announcements](<https://devfeed.tech/tags/release-announcements.md>), [scalability](<https://devfeed.tech/tags/scalability.md>), [ysql](<https://devfeed.tech/tags/ysql.md>), [yugabytedb](<https://devfeed.tech/tags/yugabytedb.md>)

### AI overview

YugabyteDB has made YSQL Connection Manager generally available in YugabyteDB 2026.1.1, YugabyteDB Anywhere, and YugabyteDB Aeon. The built-in connection pooler reduces backend connection overhead while preserving PostgreSQL session behavior, using backend pinning for features that require a single process. The announcement describes configuration options, authentication support, performance claims, and current limitations, including no support for IPv6, Unix-domain sockets, or Kerberos authentication.

### Source excerpt

We are excited to announce the General Availability (GA) of YSQL Connection Manager in YugabyteDB 2026.1.1, YugabyteDB Anywhere, and YugabyteDB Aeon. Built directly into every YugabyteDB node, YSQL Connection Manager is a native connection pooler that solves the classic trade-off between connection scalability and feature compatibility. This blog examines current PostgreSQL connection management challenges and details how YSQL Connection Manager provides seamless session-state management at scale. The post YSQL Connection Manager is Now GA appeared first on Yugabyte.

## Better HTTP/1 connection reuse

DevFeed: [Better HTTP/1 connection reuse](<https://devfeed.tech/articles/better-http-1-connection-reuse-87150.md>)

Original publisher: [Read original article](<https://go.dev/blog/http-connection-reuse>)

Author: Nicholas Husin and Damien Neil

Published: 2026-10-14T00:00:00Z

Content type: article

Language: en

Sources: [Go](<https://devfeed.tech/sources/the-go-blog.md>)

Topics: [HTTP](<https://devfeed.tech/topics/http.md>), [Java HttpClient](<https://devfeed.tech/topics/java-httpclient.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>)

Tags: [1-3](<https://devfeed.tech/tags/1-3.md>), [defer](<https://devfeed.tech/tags/defer.md>), [go](<https://devfeed.tech/tags/go.md>), [goroutine](<https://devfeed.tech/tags/goroutine.md>), [http](<https://devfeed.tech/tags/http.md>), [http-client](<https://devfeed.tech/tags/http-client.md>)

### AI overview

Go 1.27's net/http.Transport asynchronously drains unread HTTP/1 response bodies for up to 50 milliseconds or 256 KB, helping preserve connection reuse and speed up programs that make sequential requests. The article explains why unread bodies prevented reuse, describes earlier manual workarounds, and notes that this behavior may change in future Go versions.

### Source excerpt

Go 1.27 includes a change to the HTTP client that can make programs sending many sequential HTTP/1 requests significantly faster.

## Try SqlClient's new connection pool for faster parallel connections

DevFeed: [Try SqlClient's new connection pool for faster parallel connections](<https://devfeed.tech/articles/try-sqlclient-s-new-connection-pool-for-faster-parallel-connections-66412.md>)

Original publisher: [Read original article](<https://devblogs.microsoft.com/azure-sql/try-sqlclients-new-connection-pool-for-faster-parallel-connections/>)

Author: Malcolm Daigle

Published: 2026-10-06T22:42:12Z

Content type: article

Language: en

Sources: [Azure SQL Dev Corner](<https://devfeed.tech/sources/azure-sql-dev-corner.md>)

Topics: [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [Python Driver for Azure SQL](<https://devfeed.tech/topics/python-driver-for-azure-sql.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [azure-sql](<https://devfeed.tech/tags/azure-sql.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [drivers](<https://devfeed.tech/tags/drivers.md>), [net](<https://devfeed.tech/tags/net.md>), [net-9](<https://devfeed.tech/tags/net-9.md>), [sqlclient](<https://devfeed.tech/tags/sqlclient.md>)

### AI overview

Microsoft.Data.SqlClient 7.1.0 introduces an optional connection pool that opens connections concurrently. In cold-start benchmarks with 100 concurrent callers on Linux, it reduced mean completion time from 630.1 ms to 117.5 ms for synchronous opens and from 604.1 ms to 92.0 ms for asynchronous opens. The article cautions that asynchronous opens still use managed thread-pool threads for synchronous network calls, which can create pressure on high-latency connections.

### Source excerpt

You told us that applications using Microsoft.Data.SqlClient can take too long to establish the database connections they need. When many requests need connections at the same time, waiting for the connection pool to grow can delay application readiness and increase latency. This can happen even in common situations like querying several pieces of metadata during [...] The post Try SqlClient's new connection pool for faster parallel connections appeared first on Azure SQL Dev Corner.

## PostgreSQL to SQL Field Notes: Connections

DevFeed: [PostgreSQL to SQL Field Notes: Connections](<https://devfeed.tech/articles/postgresql-to-sql-field-notes-connections-65477.md>)

Original publisher: [Read original article](<https://devblogs.microsoft.com/azure-sql/pg-to-sql-connections/>)

Author: Jerry Nixon

Published: 2026-10-06T16:39:17Z

Content type: article

Language: en

Sources: [Azure SQL Dev Corner](<https://devfeed.tech/sources/azure-sql-dev-corner.md>)

Topics: [Heroku Postgres](<https://devfeed.tech/topics/heroku-postgres.md>), [sql-server](<https://devfeed.tech/topics/sql-server.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [connection draining](<https://devfeed.tech/topics/connection-draining.md>), [locking](<https://devfeed.tech/topics/locking.md>)

Tags: [antipattern](<https://devfeed.tech/tags/antipattern.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [azure-sql](<https://devfeed.tech/tags/azure-sql.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [concurrent](<https://devfeed.tech/tags/concurrent.md>), [connect](<https://devfeed.tech/tags/connect.md>), [connection-pool](<https://devfeed.tech/tags/connection-pool.md>), [connection-pooling](<https://devfeed.tech/tags/connection-pooling.md>), [cost](<https://devfeed.tech/tags/cost.md>), [database](<https://devfeed.tech/tags/database.md>), [microsoft-sql](<https://devfeed.tech/tags/microsoft-sql.md>), [modernize](<https://devfeed.tech/tags/modernize.md>), [net](<https://devfeed.tech/tags/net.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [sql](<https://devfeed.tech/tags/sql.md>), [sql-server-2025](<https://devfeed.tech/tags/sql-server-2025.md>), [t-sql](<https://devfeed.tech/tags/t-sql.md>)

### AI overview

The article compares PostgreSQL and Microsoft SQL connection models. PostgreSQL assigns a dedicated operating-system process to each connection, so developers commonly limit concurrent connections and manage pooling. Microsoft SQL uses workers on demand and typically relies on ADO.NET connection pooling, making idle connections less resource intensive. The article recommends letting the database and client pool manage most connection scenarios.

### Source excerpt

Welcome to SQL First, welcome to SQL! You're going to like this. Upgrading from PostgreSQL is real work, and depending on your old database, this process will vary widely in complexity. I am confident that you're going to love the mindful and modern features of SQL. Take your time, make the most of the resources [...] The post PostgreSQL to SQL Field Notes: Connections appeared first on Azure SQL Dev Corner.

## If Your DevOps Resume Says 5+ Years, You Should Be Able to Solve These 7 Production Problems

DevFeed: [If Your DevOps Resume Says 5+ Years, You Should Be Able to Solve These 7 Production Problems](<https://devfeed.tech/articles/if-your-devops-resume-says-5-years-you-should-be-able-to-solve-these-7-production-problems-62438.md>)

Original publisher: [Read original article](<https://blog.devops.dev/if-your-devops-resume-says-5-years-you-should-be-able-to-solve-these-7-production-problems-2cd5847cad31?source=rss----33f8b2d9a328---4>)

Author: Arvind Verma

Published: 2026-09-30T12:10:03Z

Content type: tutorial

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [incident](<https://devfeed.tech/topics/incident.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [observability](<https://devfeed.tech/topics/observability.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [health check](<https://devfeed.tech/topics/health-check.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [aws](<https://devfeed.tech/tags/aws.md>), [database](<https://devfeed.tech/tags/database.md>), [devops](<https://devfeed.tech/tags/devops.md>), [dns](<https://devfeed.tech/tags/dns.md>), [docker](<https://devfeed.tech/tags/docker.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [networking](<https://devfeed.tech/tags/networking.md>), [production](<https://devfeed.tech/tags/production.md>), [terraform](<https://devfeed.tech/tags/terraform.md>)

### AI overview

The article presents seven production troubleshooting scenarios and a common approach: define the symptom and scope, compare healthy and failing cases, follow the request or dependency path, correlate signals, validate a hypothesis, and make the smallest safe change. For Kubernetes 503s, trace traffic through ingress, service, EndpointSlices, and pods; Ready pods do not prove the full path works. High latency with low CPU points to checking waits such as database pools, queues, or downstream calls. Before applying a destructive Terraform plan, compare configuration, state, provider and module versions, execution context, and actual infrastructure. For intermittent in-cluster DNS failures, inspect the pod resolver path, CoreDNS, upstream resolvers, and network behavior. When one availability zone is slow, compare its compute, network, storage, Kubernetes, and dependency conditions with healthy zones. Low GPU utilization despite allocated VRAM can reflect a workload waiting on CPU, data, I/O, or distributed communication. After database recovery, stale connections and aggressive retries can trigger a reconnection storm, so restarting application instances blindly may worsen the issue

### Source excerpt

If your DevOps resume says 5+ years of experience, an interviewer may not be interested in asking you: "What is Kubernetes?" They may ask: "Pods are Ready. Endpoints exist. Users are still getting 503. What do you check?" That's a completely different game. Knowing Kubernetes, Terraform, AWS, networking, databases, observability, and GPUs is one thing. Knowing what signal to check next when production behaves strangely is another. Because real production incidents rarely say: "Hello engineer, the problem is in the database connection pool." They usually say: "Everything looks green. Users are still angry." And that's where production exposure matters. 😄 Let's break down seven scenarios and, more importantly, build a mental model for solving each one. 🧩 SECTION 1: FOLLOW THE REQUEST, NOT THE ERROR1 Pods Are Ready. Service Endpoints Exist. Users Still Receive 503. This is a classic Kubernetes troubleshooting scenario. You check: kubectl get pods Everything looks healthy: READY STATUS 1/1 Running Then: kubectl get endpoints my-service Endpoints exist. Yet users are getting: HTTP 503 Service Unavailable The beginner response is: "Restart the pods." Don't. First ask: Where is the 503 actually coming from? A request might travel through: User ↓ DNS ↓ Load Balancer ↓ Ingress ↓ Service ↓ Endpoint ↓ Pod ↓ Application Your pods being Ready only tells you that the readiness probe passed. It doesn't prove the entire request path is healthy. 🔎 Investigation Path Start from the outside and move inward. Check the ingress: kubectl get ingress kubectl describe ingress <name> Check the service: kubectl get svc kubectl describe svc <service> Check EndpointSlices: kubectl get endpoints kubectl get endpointslices Then test the service from inside the cluster. kubectl run debug --rm -it \ --image=curlimages/curl -- sh Then: curl http://my-service:8080/health Now you can distinguish between: Ingress problem vs. Service routing problem vs. Application problem 🏢 Production Example Imagine

## Meta's ZGateway Cuts ZippyDB Connections 19x While Handling 1B+ Operations per Second

DevFeed: [Meta's ZGateway Cuts ZippyDB Connections 19x While Handling 1B+ Operations per Second](<https://devfeed.tech/articles/meta-s-zgateway-cuts-zippydb-connections-19x-while-handling-1b-operations-per-second-60813.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/09/meta-zgateway-zippydb-proxy/>)

Author: Leela Kumili

Published: 2026-09-28T13:55:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [database-consistency](<https://devfeed.tech/topics/database-consistency.md>)

Tags: [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [availability](<https://devfeed.tech/tags/availability.md>), [caching](<https://devfeed.tech/tags/caching.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [database](<https://devfeed.tech/tags/database.md>), [development](<https://devfeed.tech/tags/development.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [fault-tolerance](<https://devfeed.tech/tags/fault-tolerance.md>), [key-value-store](<https://devfeed.tech/tags/key-value-store.md>), [load-balancing](<https://devfeed.tech/tags/load-balancing.md>), [meta-zgateway-zippydb-proxy](<https://devfeed.tech/tags/meta-zgateway-zippydb-proxy.md>), [multi-region](<https://devfeed.tech/tags/multi-region.md>), [news](<https://devfeed.tech/tags/news.md>), [reduction](<https://devfeed.tech/tags/reduction.md>), [routing](<https://devfeed.tech/tags/routing.md>), [scalability](<https://devfeed.tech/tags/scalability.md>), [service-mesh](<https://devfeed.tech/tags/service-mesh.md>)

### AI overview

Meta introduced ZGateway, a stateless proxy layer for its ZippyDB distributed key-value store, to reduce connection and reliability problems caused by a large client fleet. The gateway handles more than 1 billion operations per second and about 40% of ZippyDB traffic; Meta estimates it reduces persistent connections by roughly 19 times. It centralizes traffic management functions such as shard resolution, caching, admission control, and request batching.

### Source excerpt

Meta has introduced ZGateway, a stateless proxy for ZippyDB that centralizes connection management, traffic routing, caching, load balancing, and admission control. The gateway handles more than 1 billion operations per second and about 40% of ZippyDB traffic, while Meta's model estimates a 19x reduction in persistent connections. By Leela Kumili

## Vercel and TiDB Cloud Starter: The Full-Stack Playbook for AI Apps

DevFeed: [Vercel and TiDB Cloud Starter: The Full-Stack Playbook for AI Apps](<https://devfeed.tech/articles/vercel-and-tidb-cloud-starter-the-full-stack-playbook-for-ai-apps-60206.md>)

Original publisher: [Read original article](<https://www.pingcap.com/blog/build-with-tidb-cloud-starter-vercel-database/>)

Author: Brian Foster

Published: 2026-09-24T20:52:55Z

Content type: article

Language: en

Sources: [TiDB](<https://devfeed.tech/sources/tidb.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [TiDB](<https://devfeed.tech/topics/tidb.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>), [Database](<https://devfeed.tech/topics/database.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [Embeddings](<https://devfeed.tech/topics/embeddings.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Environment Variables](<https://devfeed.tech/topics/environment-variables.md>), [MySQL](<https://devfeed.tech/topics/mysql.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [connection-pool](<https://devfeed.tech/tags/connection-pool.md>), [database](<https://devfeed.tech/tags/database.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [dev](<https://devfeed.tech/tags/dev.md>), [distributed-sql](<https://devfeed.tech/tags/distributed-sql.md>), [embeddings](<https://devfeed.tech/tags/embeddings.md>), [environment-variables](<https://devfeed.tech/tags/environment-variables.md>), [full-stack](<https://devfeed.tech/tags/full-stack.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [tidb](<https://devfeed.tech/tags/tidb.md>), [tidb-cloud](<https://devfeed.tech/tags/tidb-cloud.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>), [vector-search](<https://devfeed.tech/tags/vector-search.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### AI overview

A practical guide to using TiDB Cloud Starter as the database for AI applications deployed on Vercel. It explains how serverless and edge runtimes affect database connections, how to store embeddings alongside application data, and how the Vercel Marketplace integration configures connection variables.

### Source excerpt

You have an AI app running on Vercel, or a prototype that v0.dev generated in a few minutes, and now it needs a real database. The choice is harder than it looks, because serverless functions and edge runtimes break the assumptions traditional databases are built on: long-lived TCP connections, a bounded pool, and a process [...] The post Vercel and TiDB Cloud Starter: The Full-Stack Playbook for AI Apps appeared first on TiDB.

## Java News Roundup: JDK 27, Open J Proxy, A2A Jakarta, Azul Payara, BoxLang, Netflix ja

DevFeed: [Java News Roundup: JDK 27, Open J Proxy, A2A Jakarta, Azul Payara, BoxLang, Netflix ja](<https://devfeed.tech/articles/java-news-roundup-jdk-27-open-j-proxy-a2a-jakarta-azul-payara-boxlang-netflix-ja-57618.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/09/java-news-roundup-sep14-2026/>)

Author: Michael Redlich

Published: 2026-09-21T17:00:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Java](<https://devfeed.tech/topics/java.md>), [releases](<https://devfeed.tech/topics/releases.md>), [Jakarta EE](<https://devfeed.tech/topics/jakarta-ee.md>), [database-scalability](<https://devfeed.tech/topics/database-scalability.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [JavaFX](<https://devfeed.tech/topics/javafx.md>), [Cache](<https://devfeed.tech/topics/cache.md>)

Tags: [agent2agent](<https://devfeed.tech/tags/agent2agent.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [azul-payara](<https://devfeed.tech/tags/azul-payara.md>), [boxlang](<https://devfeed.tech/tags/boxlang.md>), [cache](<https://devfeed.tech/tags/cache.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [connection-pool](<https://devfeed.tech/tags/connection-pool.md>), [database-scalability](<https://devfeed.tech/tags/database-scalability.md>), [developer](<https://devfeed.tech/tags/developer.md>), [development](<https://devfeed.tech/tags/development.md>), [jakarta-ee](<https://devfeed.tech/tags/jakarta-ee.md>), [java](<https://devfeed.tech/tags/java.md>), [java-news-roundup-sep14-2026](<https://devfeed.tech/tags/java-news-roundup-sep14-2026.md>), [javafx](<https://devfeed.tech/tags/javafx.md>), [jdk](<https://devfeed.tech/tags/jdk.md>), [jdk-27](<https://devfeed.tech/tags/jdk-27.md>), [jdk-28](<https://devfeed.tech/tags/jdk-28.md>), [jetbrains](<https://devfeed.tech/tags/jetbrains.md>), [jhipster](<https://devfeed.tech/tags/jhipster.md>), [ktor](<https://devfeed.tech/tags/ktor.md>), [libericajdk](<https://devfeed.tech/tags/libericajdk.md>), [netflix](<https://devfeed.tech/tags/netflix.md>), [news](<https://devfeed.tech/tags/news.md>), [open-j-proxy](<https://devfeed.tech/tags/open-j-proxy.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [release](<https://devfeed.tech/tags/release.md>), [releases](<https://devfeed.tech/tags/releases.md>)

### AI overview

A weekly roundup of Java ecosystem news covering the general availability of JDK 27, early-access JDK 28 builds, Liberica JDK 27, Jakarta EE 12 planning, Open J Proxy 1.0, and releases from several Java-related projects. It also introduces Netflix ja, a JMS command-line development experience for Java developers.

### Source excerpt

This week's Java roundup for September 14th, 2026, features news highlighting: the GA release of JDK 27, LibericaJDK 27, Open J Proxy 1.0 and A2A Jakarta 1.0; point releases of Azul Payara, JHipster, JetBrains Ktor and BoxLang; and introducing Netflix ja, a modern JMS command line development experience for Java developers. By Michael Redlich

## Connection pool sizing is a queueing theory problem, not a tuning knob

DevFeed: [Connection pool sizing is a queueing theory problem, not a tuning knob](<https://devfeed.tech/articles/connection-pool-sizing-is-a-queueing-theory-problem-not-a-tuning-knob-39593.md>)

Original publisher: [Read original article](<https://ankit-rana.com/logs/41-connection-pool-sizing-queueing-theory/>)

Author: hello@ankit-rana.com

Published: 2026-08-22T00:00:00Z

Content type: article

Language: en

Sources: [Ankit Rana | Mechanical Sympathy](<https://devfeed.tech/sources/ankit-rana-mechanical-sympathy.md>)

Topics: [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [queueing theory](<https://devfeed.tech/topics/queueing-theory.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [Database](<https://devfeed.tech/topics/database.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>)

Tags: [capacity-planning](<https://devfeed.tech/tags/capacity-planning.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [connection-pool](<https://devfeed.tech/tags/connection-pool.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [database](<https://devfeed.tech/tags/database.md>), [database-performance](<https://devfeed.tech/tags/database-performance.md>), [hikaricp](<https://devfeed.tech/tags/hikaricp.md>), [inference](<https://devfeed.tech/tags/inference.md>), [latency](<https://devfeed.tech/tags/latency.md>), [network](<https://devfeed.tech/tags/network.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [query](<https://devfeed.tech/tags/query.md>), [queueing-theory](<https://devfeed.tech/tags/queueing-theory.md>)

### AI overview

This article explains how to size a connection pool using Little's law: concurrency equals throughput multiplied by connection holding time. It argues that increasing the pool beyond the database's parallel execution capacity can move the queue, increase latency, and leave throughput flat. It also identifies excessive holding time from network round trips, N+1 queries, long transactions, and model inference calls as common causes of pool exhaustion.

### Source excerpt

Pool size follows from Little's law: concurrency equals throughput multiplied by holding time, so 500 requests per second each holding a connection for 20ms needs ten connections rather than a round number someone picked. Past the point where the database can execute requests in parallel, adding connections moves the queue rather than removing it, and latency grows while throughput stays flat. The number that actually reaches the database is the pool size multiplied by the instance count, which is usually the number nobody has calculated.

## Promotions are Proactive: The 3P Framework for Pitching Your Next Level

DevFeed: [Promotions are Proactive: The 3P Framework for Pitching Your Next Level](<https://devfeed.tech/articles/promotions-are-proactive-the-3p-framework-for-pitching-your-next-level-39583.md>)

Original publisher: [Read original article](<https://ankit-rana.com/logs/31-promotions-proactive-3p-framework/>)

Author: hello@ankit-rana.com

Published: 2026-08-02T00:00:00Z

Content type: opinion

Language: en

Sources: [Ankit Rana | Mechanical Sympathy](<https://devfeed.tech/sources/ankit-rana-mechanical-sympathy.md>)

Topics: [Back end](<https://devfeed.tech/topics/backend.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [migration](<https://devfeed.tech/topics/migration.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [caching](<https://devfeed.tech/tags/caching.md>), [career](<https://devfeed.tech/tags/career.md>), [career-growth](<https://devfeed.tech/tags/career-growth.md>), [connection-pool](<https://devfeed.tech/tags/connection-pool.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [latency](<https://devfeed.tech/tags/latency.md>), [leadership](<https://devfeed.tech/tags/leadership.md>), [migration](<https://devfeed.tech/tags/migration.md>), [scope](<https://devfeed.tech/tags/scope.md>), [system-design](<https://devfeed.tech/tags/system-design.md>)

### AI overview

This article presents the 3P framework--Problem, Proof, and Proactive pitch--for making an engineer's promotion case legible before review. It argues that promotion reflects the scope or blast radius of decisions, supported by system evidence and an explicit pitch.

### Source excerpt

Promotion committees do not promote effort, they promote scope, and scope has to be legible before the vote rather than explained after it fails. Strip the leveling-guide language and the question is blast radius: a mid-level engineer's bad call fails one deploy unit, a senior's saturates a pool at 2 AM across teams. The 3P framework makes that visible: Problem at org scale, Proof in system metrics, and a Proactive pitch.

## We put Bun's Rust rewrite in production on Prisma Compute

DevFeed: [We put Bun's Rust rewrite in production on Prisma Compute](<https://devfeed.tech/articles/we-put-bun-s-rust-rewrite-in-production-on-prisma-compute-47571.md>)

Original publisher: [Read original article](<https://www.prisma.io/blog/bun-rust-rewrite-prisma-compute>)

Author: Alexey Orlenko

Published: 2026-06-11T00:00:00Z

Content type: article

Language: en

Sources: [Prisma](<https://devfeed.tech/sources/prisma-blog.md>)

Topics: [Bun](<https://devfeed.tech/topics/bun.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [reliability-engineering](<https://devfeed.tech/topics/reliability-engineering.md>), [Rust](<https://devfeed.tech/topics/rust.md>), [Memory Leaks](<https://devfeed.tech/topics/memory-leaks.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>)

Tags: [bun](<https://devfeed.tech/tags/bun.md>), [connection-pool](<https://devfeed.tech/tags/connection-pool.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [memory](<https://devfeed.tech/tags/memory.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [production](<https://devfeed.tech/tags/production.md>), [rust](<https://devfeed.tech/tags/rust.md>), [scale](<https://devfeed.tech/tags/scale.md>)

### AI overview

Prisma explains why Prisma Compute's public beta launched on Bun's Rust rewrite canary. Testing under real load exposed memory leaks and connection-pool recovery failures in Bun 1.3, while the rewrite handled those failure modes and avoided maintaining a growing private fork.

### Source excerpt

Why Prisma Compute's public beta runs on Bun's Rust rewrite canary: the memory and connection-pool failures we hit on stable Bun, and what changed.

## AI agents break connection pooling by holding the slot while they think

DevFeed: [AI agents break connection pooling by holding the slot while they think](<https://devfeed.tech/articles/ai-agents-break-connection-pooling-by-holding-the-slot-while-they-think-39573.md>)

Original publisher: [Read original article](<https://ankit-rana.com/logs/21-llms-connection-pooling-ai-agents/>)

Author: hello@ankit-rana.com

Published: 2026-03-21T00:00:00Z

Content type: article

Language: en

Sources: [Ankit Rana | Mechanical Sympathy](<https://devfeed.tech/sources/ankit-rana-mechanical-sympathy.md>)

Topics: [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [Database](<https://devfeed.tech/topics/database.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Back end](<https://devfeed.tech/topics/backend.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [concurrent](<https://devfeed.tech/tags/concurrent.md>), [connection-pool](<https://devfeed.tech/tags/connection-pool.md>), [connection-pooling](<https://devfeed.tech/tags/connection-pooling.md>), [databases](<https://devfeed.tech/tags/databases.md>), [latency](<https://devfeed.tech/tags/latency.md>), [llm](<https://devfeed.tech/tags/llm.md>), [performance](<https://devfeed.tech/tags/performance.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>)

### AI overview

This article explains how AI agents can exhaust database connection pools by holding connections during LLM inference. It describes the resulting queueing and latency problems, including cases where the database remains lightly loaded, and recommends releasing the connection before calling the model.

### Source excerpt

Connection pooling assumes an implicit contract that transactions stay microscopic, roughly 50 ms of database time per request. An agent that holds a pooled connection while waiting 3 to 5 seconds for LLM inference breaks that assumption: 100 concurrent agents can occupy every slot in a 100-connection pool while the database sits at 2 percent CPU. Fetch, release the connection immediately, then call the model asynchronously.

## Bun v1.3.4

DevFeed: [Bun v1.3.4](<https://devfeed.tech/articles/bun-v1-3-4-49456.md>)

Original publisher: [Read original article](<https://bun.com/blog/bun-v1.3.4>)

Author: Jarred Sumner

Published: 2025-12-06T10:11:00Z

Content type: release

Language: en

Sources: [Bun](<https://devfeed.tech/sources/bun-com.md>)

Topics: [Bun](<https://devfeed.tech/topics/bun.md>), [Web APIs](<https://devfeed.tech/topics/web-apis.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [pattern matching](<https://devfeed.tech/topics/pattern-matching.md>), [test](<https://devfeed.tech/topics/test.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [fetch](<https://devfeed.tech/topics/fetch.md>), [proxy](<https://devfeed.tech/topics/proxy.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [bun](<https://devfeed.tech/tags/bun.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [connection-pooling](<https://devfeed.tech/tags/connection-pooling.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [fetch](<https://devfeed.tech/tags/fetch.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [test](<https://devfeed.tech/tags/test.md>), [v1](<https://devfeed.tech/tags/v1.md>), [web-apis](<https://devfeed.tech/tags/web-apis.md>)

### AI overview

Bun v1.3.4 is a release covering URLPattern support with declarative URL matching, fake timers in bun:test, custom proxy headers, connection-pooling fixes, standalone executable configuration changes, and additional compatibility and platform bug fixes.

### Source excerpt

Fixes 194 issues (addressing 412 👍). URLPattern API, Fake Timers for bun:test, Custom Proxy Headers in fetch(),console.log %j format, http.Agent connection pooling fix, Standalone executable config loading changes, SQLite 3.51.1, and numerous bugfixes for bun:test, Node.js compatibility, Windows, Web APIs, bun install, and more

## Cloudflare, Unikernels & Bare Metal: Life of a Prisma Postgres Query

DevFeed: [Cloudflare, Unikernels & Bare Metal: Life of a Prisma Postgres Query](<https://devfeed.tech/articles/cloudflare-unikernels-bare-metal-life-of-a-prisma-postgres-query-47578.md>)

Original publisher: [Read original article](<https://www.prisma.io/blog/cloudflare-unikernels-and-bare-metal-life-of-a-prisma-postgres-query>)

Author: Nikolas Burk

Published: 2025-02-05T00:00:00Z

Content type: article

Language: en

Sources: [Prisma](<https://devfeed.tech/sources/prisma-blog.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Prisma](<https://devfeed.tech/topics/prisma.md>), [Database](<https://devfeed.tech/topics/database.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [Object-relational mapping](<https://devfeed.tech/topics/orm.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [Cloudflare Workers](<https://devfeed.tech/topics/cloudflare-workers.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [Cloudflare](<https://devfeed.tech/topics/cloudflare.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>)

Tags: [caching](<https://devfeed.tech/tags/caching.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloudflare-workers](<https://devfeed.tech/tags/cloudflare-workers.md>), [connection-pool](<https://devfeed.tech/tags/connection-pool.md>), [database](<https://devfeed.tech/tags/database.md>), [developers](<https://devfeed.tech/tags/developers.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [prisma](<https://devfeed.tech/tags/prisma.md>)

### AI overview

An under-the-hood look at how Prisma Postgres processes queries through Prisma ORM, connection pooling, caching, Cloudflare Workers, unikernels, and underlying infrastructure. It describes the database's serverless architecture and related performance and pricing features.

### Source excerpt

Take a look under the hood of the most innovative PostgreSQL database on the market and learn how a query travels through Cloudflare, unikernels and bare metal.

## Prisma Postgres: A Serverless Database with Zero Cold Starts, Edge Caching, and Connection Pooling

DevFeed: [Prisma Postgres: A Serverless Database with Zero Cold Starts, Edge Caching, and Connection Pooling](<https://devfeed.tech/articles/prisma-postgres-the-future-of-serverless-databases-47746.md>)

Original publisher: [Read original article](<https://www.prisma.io/blog/prisma-postgres-the-future-of-serverless-databases>)

Author: Nikolas Burk

Published: 2025-02-03T00:00:00Z

Content type: article

Language: en

Sources: [Prisma](<https://devfeed.tech/sources/prisma-blog.md>)

Topics: [Database](<https://devfeed.tech/topics/database.md>), [Prisma](<https://devfeed.tech/topics/prisma.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>)

Tags: [caching](<https://devfeed.tech/tags/caching.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [connection-pooling](<https://devfeed.tech/tags/connection-pooling.md>), [databases](<https://devfeed.tech/tags/databases.md>), [edge](<https://devfeed.tech/tags/edge.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [pricing](<https://devfeed.tech/tags/pricing.md>), [prisma](<https://devfeed.tech/tags/prisma.md>), [serverless](<https://devfeed.tech/tags/serverless.md>)

### AI overview

Prisma Postgres is a production-ready serverless database built on unikernels, Cloudflare infrastructure, and bare-metal machines. The article describes zero cold starts, global edge caching, built-in connection pooling, usage-based pricing, and a free tier, along with AI-generated query insights.

### Source excerpt

Prisma Postgres is finally ready for production! Built on unikernels, it enables a unique set of benefits like no cold starts, connection pooling, edge caching, & more!

## How to Handle Database Connection Pooling

DevFeed: [How to Handle Database Connection Pooling](<https://devfeed.tech/articles/how-to-handle-database-connection-pooling-95534.md>)

Original publisher: [Read original article](<https://blog.railway.com/p/database-connection-pooling>)

Published: 2024-12-13T00:00:00Z

Content type: tutorial

Language: en

Sources: [Railway](<https://devfeed.tech/sources/railway.md>)

Topics: [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>), [Database](<https://devfeed.tech/topics/database.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>)

Tags: [applications](<https://devfeed.tech/tags/applications.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [connection-pooling](<https://devfeed.tech/tags/connection-pooling.md>), [database](<https://devfeed.tech/tags/database.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [performance](<https://devfeed.tech/tags/performance.md>), [railway](<https://devfeed.tech/tags/railway.md>)

### AI overview

Connection pooling reuses a limited set of database connections across queries, avoiding repeated connection setup and teardown. The article demonstrates normal and pooled connections with Node.js, PostgreSQL's `pg` library, and Prometheus histograms. In its reported 100-query comparison, pooled queries took almost three times less total time; all pooled queries finished within 5 ms, while only 98 normal queries finished within 10 ms. These are demonstration results, and the article notes that Railway hosting adds network latency. Pools require sizing: too few connections can leave requests waiting, while too many waste resources. The article also cites shared-connection security concerns and the pool as an added component and potential single point of failure. It suggests that small applications may not benefit enough to justify the added complexity.

### Source excerpt

Understand database connection pooling and how it helps improve performance of your applications

[Next page](<https://devfeed.tech/topics/connection-pool.md?cursor=WyIyMDI0LTEyLTEzVDAwOjAwOjAwKzAwOjAwIiwgIjlmZDBkZjIzLWZiYzctNDRlNy1iNWJhLTllZTNjMDY0NTI5ZiJd>)