Workers & Storage
The account runs 31 Workers. They fall into four groups by purpose and age: the active platform/API build, the marketing and CMS surface, a set of recent documentation demos, and a long tail of legacy ad and utility Workers.
Platform / API (active build)
Section titled “Platform / API (active build)”These are the Workers under active development in 2026, all on the dev tier, following the adv-{category}-{project}-{env} naming convention.
| Worker | Purpose |
|---|---|
adv-svc-public-api-dev | Public API service (Hyperdrive-backed) |
adv-svc-admin-api-dev | Admin API |
adv-svc-auth-helper-dev | Authentication helper (KV cache) |
adv-ui-admin-dev | Admin UI (genesis-admin) |
adv-ui-productlove-dev | ProductLove UI |
adv-svc-newrelic-proxy-dev | New Relic ingest proxy (Access-protected) |
adventive-tools-gateway-worker-dev | Internal tools gateway (tools.adventive.io) |
adventive-status-worker-dev | Status dashboard (reference storage implementation) |
Marketing / CMS
Section titled “Marketing / CMS”adventive-cms, adventive-marketing-cms, adventive-marketing-frontend (and its -staging sibling), adventivestg-com, cms-integration-adventivestg-com, adv-site-marketing-cms-dev, and adventive-prototype-guidelines. These bind the marketing D1 databases and R2 media buckets and serve the CMS and marketing site surfaces.
Documentation demos
Section titled “Documentation demos”adventive-docs-demo-lucode, adventive-docs-demo-next, adventive-docs-demo-nova, and adventive-docs-sandbox. All created in July 2026 as evaluation and demo scaffolds.
Legacy / ad & utility
Section titled “Legacy / ad & utility”edgecache-ad-router and edgecache-ad-router-production, geo, stats, zipsearch, latest-post-title, plugshare, plugshare-test, plugshare001, 1x1, and test-worker. Several of these have not been modified since 2022-2024. edgecache-ad-router-production is still live on ads.adventivecdn.com/ad*, and plugshare/plugshare-test were touched as recently as July 2026, so the group is a mix of live and dormant. This group is the best candidate for an ownership-and-retention review: confirm which are still serving traffic, assign an owner, and retire the rest.
Storage & data
Section titled “Storage & data”All storage resources are on the dev tier today, consistent with the platform build being pre-production.
Hyperdrive: 3 configs
Section titled “Hyperdrive: 3 configs”adv-svc-public-api-console-dev, adv-svc-public-api-aggregate-dev, and adv-svc-public-api-billing-dev. Each pools connections to a MySQL database (console, aggregate, billing) reached over the adv-cflared-dev tunnel with a 60-connection origin limit and caching enabled. All three authenticate with the shared adv-hyperdrive-dev Access service token. See Zero Trust & Security for the full access chain.
KV: 8 namespaces
Section titled “KV: 8 namespaces”CACHE_KV, dev-SESSION_KV, dev-IDEMPOTENCY_KV, rate-limit-kv-dev, kv-adv-svc-auth-helper-cache-dev, adv-status-snapshot-dev, adv-site-marketing-cms-dev-session, and development. The naming is mostly consistent; development and CACHE_KV predate the current convention and could be renamed or retired if unused.
D1: 3 databases
Section titled “D1: 3 databases”adv-status-db-dev, adventive-cms-db, and d1-adv-site-marketing-cms-dev. All report zero tables in the API metadata, which reflects D1’s edge storage model rather than empty databases.
R2: 8 buckets
Section titled “R2: 8 buckets”static-adventive-com, gallery-adventive-com, email-adventivecdn-com, adventive-university, adventive-cms-media, r2-adv-site-marketing-cms-dev, adv-status-artifacts-dev, and adv-status-artifacts-dev-replica. The status artifacts bucket is the only one with an explicit paired replica. A deliberate backup posture worth extending to other buckets that hold non-reproducible data.
Queues: 2
Section titled “Queues: 2”adv-status-alerts-dev and its dead-letter queue adv-status-alerts-dev-dlq. The main queue has a wired producer and consumer; the dead-letter queue is the failure sink.
The status dashboard (adventive-status-worker-dev) is the most fully instrumented service in the account. It binds D1, KV, R2 with a replica, and a Queue plus dead-letter queue, which makes it the working reference for the platform’s storage pattern.