Connection pooling in GraphQL - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a connection pool with a maximum of 10 connections.

GraphQL

const pool = new Pool({ max: [1] });

Drag options to blanks, or click blank then click option'

A10

B5

C20

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Setting max to 1 limits to a single connection, which is not pooling.

Using too high a number can overload the database.

The max property sets the maximum number of connections in the pool. Here, 10 is the correct value.

2fill in blank

medium

Complete the code to acquire a client from the connection pool.

GraphQL

const client = await pool.[1]();

Drag options to blanks, or click blank then click option'

AgetClient

Bconnect

Cacquire

Dopen

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent methods like 'getClient' causes errors.

Forgetting to await the async method leads to unresolved promises.

The connect() method is used to get a client from the pool.

3fill in blank

hard

Fix the error in releasing the client back to the pool.

GraphQL

client.[1]();

Drag options to blanks, or click blank then click option'

Adisconnect

Bclose

Crelease

Dend

Attempts:

3 left

💡 Hint

Common Mistakes

Calling 'end' closes the connection permanently, defeating pooling.

Forgetting to release causes connection leaks.

The release() method returns the client to the pool for reuse.

4fill in blank

hard

Fill both blanks to create a query using a pooled client and release it after.

GraphQL

const client = await pool.[1]();
const res = await client.query('SELECT * FROM users');
client.[2]();

Drag options to blanks, or click blank then click option'

Aconnect

Brelease

Cend

Ddisconnect

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'end' or 'disconnect' closes the connection permanently.

Not releasing the client causes connection exhaustion.

You must connect() to get the client and release() it after the query.

5fill in blank

hard

Fill all three blanks to configure a pool with max 15 connections, idle timeout 30000 ms, and statement timeout 5000 ms.

GraphQL

const pool = new Pool({ max: [1], idleTimeoutMillis: [2], statement_timeout: [3] });

Drag options to blanks, or click blank then click option'

A15

B30000

C5000

D10000

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up timeout values or using wrong property names.

Setting max too low or too high can cause performance issues.

The max sets max connections, idleTimeoutMillis sets idle timeout, and statement_timeout sets statement timeout in milliseconds.

Practice

1. What is the main purpose of connection pooling in a GraphQL database context?

easy

A. To reuse database connections and improve performance

B. To create a new connection for every query

C. To store query results permanently

D. To encrypt database connections

Solution

1. Step 1: Understand connection pooling concept

   Connection pooling means reusing existing database connections instead of opening new ones each time.

2. Step 2: Identify the benefit in GraphQL context

   Reusing connections reduces delay and resource use, improving performance when many queries happen.

3. Final Answer:

   To reuse database connections and improve performance -> Option A

4. Quick Check:

   Connection pooling = reuse connections [OK]

Hint: Pooling means reuse connections, not create new ones [OK]

Common Mistakes:

• Thinking pooling creates new connections each time
• Confusing pooling with data caching
• Assuming pooling encrypts connections

2. Which of the following is the correct way to release a connection back to the pool in a typical GraphQL server setup?

easy

A. connection.release()

B. connection.close()

C. connection.disconnect()

D. connection.terminate()

Solution

1. Step 1: Identify common connection pool methods

   Most connection pools provide a release() method to return the connection to the pool.

2. Step 2: Differentiate from close or disconnect

   close() or disconnect() usually close the connection permanently, not return it to the pool.

3. Final Answer:

   connection.release() -> Option A

4. Quick Check:

   Release method returns connection to pool [OK]

Hint: Use release() to return connection, not close() [OK]

Common Mistakes:

• Using close() which ends connection permanently
• Confusing disconnect() with release()
• Not releasing connections causing pool exhaustion

3. Given this pseudo-code snippet in a GraphQL resolver using connection pooling:

const conn = pool.getConnection();
const result = await conn.query('SELECT * FROM users');
conn.release();
return result;

What will happen if conn.release() is omitted?

medium

A. The connection stays open and is reused properly

B. The connection is closed and cannot be reused

C. The connection remains checked out, reducing available connections

D. The query will fail immediately

Solution

1. Step 1: Understand connection release role

   Calling release() returns the connection to the pool for reuse by others.

2. Step 2: Consequence of omitting release()

   If release() is not called, the connection stays checked out and unavailable for others, reducing pool capacity.

3. Final Answer:

   The connection remains checked out, reducing available connections -> Option C

4. Quick Check:

   Omitting release() = connection not returned [OK]

Hint: Always release connections to keep pool healthy [OK]

Common Mistakes:

• Assuming connection closes automatically
• Thinking query fails without release
• Believing connection is reused without release

4. You see this error in your GraphQL server logs: "Pool exhausted: no available connections." What is the most likely cause?

medium

A. The database server is down

B. Connections are not being released back to the pool

C. The GraphQL schema is invalid

D. The query syntax is incorrect

Solution

1. Step 1: Interpret the error message

   "Pool exhausted" means all connections are checked out and none are free to use.

2. Step 2: Identify common cause

   This usually happens if connections are not released properly after use, causing depletion.

3. Final Answer:

   Connections are not being released back to the pool -> Option B

4. Quick Check:

   Pool exhausted = no released connections [OK]

Hint: Pool exhausted means connections not released [OK]

Common Mistakes:

• Blaming database downtime without checking pool
• Confusing schema errors with connection issues
• Assuming query syntax causes pool exhaustion

5. In a GraphQL API using connection pooling, you want to optimize performance for a high-traffic endpoint. Which approach best combines connection pooling with query batching to reduce database load?

hard

A. Disable connection pooling and rely on caching only

B. Open a new connection for each GraphQL query and run them separately

C. Use connection pooling but run each query individually without batching

D. Use connection pooling and batch multiple GraphQL queries into one database query

Solution

1. Step 1: Understand connection pooling and batching

   Connection pooling reuses connections; batching combines multiple queries into one to reduce load.

2. Step 2: Combine both for optimization

   Batching queries reduces number of database calls; pooling ensures connections are reused efficiently.

3. Step 3: Evaluate options

   Opening new connections or disabling pooling wastes resources; not batching misses optimization.

4. Final Answer:

   Use connection pooling and batch multiple GraphQL queries into one database query -> Option D

5. Quick Check:

   Pooling + batching = best performance [OK]

Hint: Combine pooling with batching for best speed [OK]

Common Mistakes:

• Opening new connections each time wastes resources
• Disabling pooling loses reuse benefits
• Not batching queries increases load