Question 1

How do I create a database connection pool with Poolboy in Erlang?

Accepted Answer

Refer to the example in the README: define pool configurations in your .app file, create a worker module implementing gen_server and poolboy_worker behaviors, and use poolboy:transaction for queries. This involves setting parameters like size, max_overflow, and database credentials.

Question 2

What's the difference between LIFO and FIFO in Poolboy's checkout strategy?

Accepted Answer

LIFO (last-in, first-out) operates like a stack, reusing the most recently checked-in workers first, while FIFO (first-in, first-out) works like a queue, ensuring older workers are reused first. The default is LIFO, which can improve efficiency for certain workloads by reducing setup overhead.

Question 3

Poolboy vs OTP supervisors: which one should I use for worker management?

Accepted Answer

Poolboy is specialized for pooling reusable workers like database connections, offering optimized checkout/checkin and overflow handling. OTP supervisors are better for general process supervision and restart strategies without pooling. Use Poolboy when you need efficient resource reuse; use supervisors for fault tolerance in non-pooled scenarios.

Question 4

How does Poolboy handle worker crashes and ensure reliability?

Accepted Answer

Poolboy is designed for disaster recovery; when a worker crashes, it can be restarted by the supervision tree. However, you must implement proper error handling in your worker module, as shown in the example with trap_exit and terminate functions to clean up resources.

Question 5

Can I use Poolboy with Elixir projects, and how?

Accepted Answer

Yes, Poolboy is an Erlang library and is compatible with Elixir since both run on the BEAM VM. Include it as a dependency in your mix.exs file and call its functions directly, similar to Erlang usage, or wrap it in Elixir modules for better integration.

Question 6

What are best practices for setting max_overflow in Poolboy?

Accepted Answer

Set max_overflow based on your application's burst traffic needs; it defines extra workers created when the pool is empty. A higher value handles spikes better but increases resource usage. Since Poolboy lacks built-in metrics, monitor your pool's usage empirically to tune it appropriately.

poolboy

What is poolboy?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions