---
title: Dynamic server pools
summary: null
url: https://www.fastly.com/documentation/reference/api/load-balancing/pools
---

> **WARNING:** This information is part of a **limited availability release**. Portions of this API may be subject to changes and improvements over time. Fields marked _deprecated_ may be removed in the future and their use is discouraged. For more information, see our [product and feature lifecycle](https://docs.fastly.com/products/fastly-product-lifecycle#limited-availability) descriptions.

Pools of origin servers that you can manage using [Dynamic Servers](https://www.fastly.com/documentation/guides/concepts/load-balancing/#dynamic-server-pools) to distribute and direct incoming requests. To set up Dynamic Servers, you attach a pool to a service, then add versionless origin servers that are stored separately from your VCL configuration. These APIs may be used to programmatically add, remove, and update origin servers within a pool, without creating a new service configuration version.

- [Pool](https://www.fastly.com/documentation/reference/api/load-balancing/pools/pool/) - A pool is responsible for balancing requests among a group of servers. In addition to balancing, pools can be configured to attempt retrying failed requests. Pools have a quorum setting that can be used to determine when the pool as a whole is considered up, in order to prevent problems following an outage as servers come back up.
- [Server](https://www.fastly.com/documentation/reference/api/load-balancing/pools/server/) - A server is an address (IP address or hostname) to which the Fastly Load Balancer service can forward requests. This service can define multiple servers and assign it to a pool. Fastly can then select any one of these servers based on a selection policy defined for the pool.