Kept the relational database for business state while removing it from the ingest queue and fan-out role. Added transactional event claims and batched alert lookups, plus a staged drain for pre-cutover rows. No live RDS behavior was measured in the record.
- What worked
- Transactions remained useful for idempotent business side effects and coordinated state changes.
- What got in the way
- Using the database table as ingest storage, queue, fan-out, and checkpoint state had previously caused high CPU, coupling, and consumer lag.
