Nitric · Rate Limits

Nitric Rate Limits

Nitric is a framework / IaC SDK and CLI, not a hosted API, so Nitric itself imposes no API rate limits or quotas. Any throttling experienced by an application built with Nitric comes from the underlying cloud services that the chosen provider plugin provisions - for example AWS API Gateway request quotas, SQS throughput limits, DynamoDB capacity, or cloud-account service quotas on AWS, Google Cloud, or Azure. Specific limits depend entirely on the target cloud and the resources declared, and are not reconciled in this artifact.

Nitric Rate Limits is the machine-readable rate-limit profile for Nitric on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring requests.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Infrastructure from Code, Cloud Framework, SDK, CLI, and Rate Limiting.

2 Limits Throttle: 429
Infrastructure from CodeCloud FrameworkSDKCLIRate LimitingQuotas

Limits

Framework Rate Limits framework
requests
not applicable
Nitric is an SDK/CLI; it does not meter or throttle API calls itself.
Cloud Provider Service Quotas account
requests
see target cloud documentation
Throttling derives from the provisioned cloud services (e.g. AWS API Gateway, SQS, SNS, DynamoDB) and the cloud account's service quotas.

Policies

Cloud-Native Quotas
Effective limits are defined by the target cloud provider's service quotas for the resources Nitric provisions, not by Nitric.
Backoff Strategy
Applications should implement exponential backoff with jitter and honor Retry-After when calling provisioned cloud services that return 429.

Sources