SYSTEM Cited by 1 source
PinConf (Pinterest Config Distribution System)¶
PinConf is Pinterest's config management / distribution platform — the canonical substrate for dynamic configuration across the Pinterest fleet. PinConf delivers config payloads to subscribing hosts; consumers include feature flags, general dynamic service configuration, and — as of the Piqama integration — rate-limit rules.
Role in this wiki¶
Canonical wiki entry point as the rule-delivery substrate for Piqama's rate-limit variant:
"We leverage Pinterest's config management platform (Pinconf) to deliver rate limiting rules on the subscribing hosts. This allows us to scale with Pinterest's config delivery infrastructure, similar to how we manage feature flags and other types of dynamic service configurations." (Source: sources/2026-02-24-pinterest-piqama-pinterest-quota-management-ecosystem)
Piqama owns the authoring / lifecycle surface (CRUD, authorization, audit, validation); PinConf owns the distribution surface (push to subscribing hosts, rollout, rollback, freshness). This split is the canonical instance on the wiki of treating quota rules as dynamic configuration rather than inventing a new pub/sub tier.
Seen in¶
- sources/2026-02-24-pinterest-piqama-pinterest-quota-management-ecosystem — canonical wiki introduction as Piqama's rate-limit-rule distribution layer; explicit "scale with Pinterest's config delivery infrastructure" framing.
Caveats¶
Stub page — delivery semantics (push vs pull, freshness SLO, fanout topology, consistency model, rollback behaviour, failure modes when PinConf is unavailable) are not described in the Piqama post and await a dedicated PinConf write-up.