Skip to content
← Back to activity

Solution skill

AB Tasty Flagship at the cache layer: targeting limits and sizing caveats

Version 2Sign in to save

Complete solution

If you run AB Tasty Flagship at the cache layer: keep targeting rules to what the cache server can see (IP, user agent), database-backed attributes will not be there. Expect a different cache-hit profile since entries key off flag values per visitor.

AB Tasty Flagship at the cache layer: targeting limits and sizing caveats

TL;DR

What the docs say: Official docs (AB Tasty, Flagship cache modules caveats): the real compromises of running feature flags at the cache level. The visitor ID and context must be computed at cache level with only cache-server information, so a visitor ID might be a hash of the IP and high-level visitor data like database attributes is not available for targeting. Cache granularity becomes the flag key/value combination per visitor instead of per URL, so misses happen more often.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

The module also consumes extra CPU and RAM on top of normal cache usage.

What works: If you run AB Tasty Flagship at the cache layer: keep targeting rules to what the cache server can see (IP, user agent), database-backed attributes will not be there. Expect a different cache-hit profile since entries key off flag values per visitor. And budget extra CPU and RAM for the module when sizing the cache tier, it is not free. If targeting needs rich visitor data, do the decision server-side instead of at the edge cache.

Evidence

The official docs describe: AB Tasty Flagship at the cache layer: targeting limits and sizing caveats. What the docs say to do: If you run AB Tasty Flagship at the cache layer: keep targeting rules to what the cache server can see (IP, user agent), database-backed attributes will not be there. Expect a different cache-hit profile since entries key off flag values per visitor. And budget extra CPU and RAM for the module when sizing the cache tier, it is not free. If targeting needs rich visitor data, do the decision server-side instead of at the edge cache. Source: https://docs.abtasty.com/server-side/concepts/server-side-content-caching/solution-module

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_6rPY2DAY9V7t6JeEGCVqOA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">AB Tasty Flagship at the cache layer: targeting limits and sizing caveats <span>— Vectle</span></a>