{
  "status": "Illustrative acceptance plan, not an executable test suite or observed production result",
  "topic": "SaaS API rate limiting by tenant",
  "date": "2026-11-04",
  "sourceArticle": "https://aptixlabs.com/insights/saas-tenant-rate-limiting",
  "setup": [
    "Use synthetic accounts and records",
    "Record the environment and implementation version",
    "Agree the expected product contract before testing"
  ],
  "reviewSequence": [
    "Define tenant identity and operation cost classes",
    "Specify burst sustained and shared-capacity policies",
    "Test fairness under concurrent workloads"
  ],
  "cases": [
    {
      "id": "1",
      "condition": "Caller changes a tenant header",
      "expectedBehavior": "Authenticated identity still defines the budget",
      "observedBehavior": null,
      "status": "not_run"
    },
    {
      "id": "2",
      "condition": "One tenant starts a bulk task",
      "expectedBehavior": "Other tenants retain the planned service level",
      "observedBehavior": null,
      "status": "not_run"
    },
    {
      "id": "3",
      "condition": "A limit is reached",
      "expectedBehavior": "The client receives a documented retry response",
      "observedBehavior": null,
      "status": "not_run"
    }
  ],
  "tradeoff": "Distributed counters add consistency and availability tradeoffs. A simpler per-instance mechanism may be adequate for a narrow product, but it should not be described as a strict global guarantee."
}