Hear from Slack, the ACLU, TED, & more at our customer summit in San Francisco Register
LOG IN SIGN UP
Documentation

About Dynamic Servers

  Last updated April 19, 2017

Fastly's Dynamic Servers feature distributes and directs incoming requests to a pool of servers that you dynamically manage. The benefits to using Dynamic Servers include:

To set up Dynamic Servers, you attach a pool to a service, then add versionless server entries that are stored separately from your VCL configuration. You can use the Fastly API to programmatically add, remove, and update pools and server entries.

How Dynamic Servers work

Like Edge Dictionaries and Edge ACLs, Dynamic Servers have two major components: the pool and the server entries within it. Pools act as containers for server entries that store the hostnames or IP addresses of servers to which incoming requests can be directed. Each pool is attached to a version of a service, but server entries are versionless and any changes will become effective immediately.

When Dynamic Servers might be useful

Dynamic Servers might be useful for organizations that need to load balance requests among servers in a single region, such as AWS EC2 instances in the US East region. They're also useful for evaluating new server instance types and new software deployments. Dynamic Servers are a great way to scale micro services.

Getting started

You'll need to follow these steps:

  1. Create an empty pool in a working version of a service that's unlocked and not yet activated.
  2. Activate the new version of the service you associated with the empty pool.
  3. Add server entries to the newly created pool, keeping in mind the limitations.

Once the pool is created, properly associated, and filled with server entries, it can be called in your service.

Limitations

Keep the following limitations in mind as you use Dynamic Servers:


Additional resources:


Back to Top