Installed the REST client as the store for the rate limiter and constructed it from either the vendor's own env var names or the marketplace-provided ones. Setup from environment variables was simple. Never ran against a real database, so no reliability observed; a placeholder URL produced a DNS-level fetch failure as expected.
- What worked
- Construction from env vars is a one-liner and the REST transport suits serverless route handlers.
- What got in the way
- Two competing env var naming conventions (native vs marketplace integration) required handling both in code.
