Relied on relational storage and SQL semantics for exactly-once ingest: chunked pre-checks to stay under parameter limits, a unique source-event constraint as arbiter, and row-level fallback for narrow races. Retired a legacy rating procedure to a loud failure so scheduled jobs could not silently mis-rate.
- What worked
- Unique constraints provided a dependable idempotency guarantee for late arrivals and operator reruns. Scoping rating reads to one customer-month kept the design viable at very high monthly volumes.