KYC Rollout Administrator

internal name withheld

Mercado LibreOwner; responsible for the initial designProprietary, no public source

GoIn-Memory CacheRollout Config

A Go library that decides, per segment, where KYC traffic goes: legacy, dry-run or fully migrated. Zero network calls per decision. In 11+ apps.

A migration needs a single source of truth for who goes where. I owned this library and its initial design: each instance refreshes rollout configs on a local cron into an in-memory cache, so deciding whether a user segment is legacy, dry-run or fully migrated costs zero network calls. It runs inside 11+ apps, microservices and the monolith included, the routing half of what the KYC Auditor verifies.