I looked up retention, ordering keys, exactly-once delivery, and timestamp seek to see if a subscription could replace the shared table. Ordering keys exist, but retention was about 31 days, too tight for a 30-day replay with margin, and seek together with exactly-once delivery was described as eventually consistent. That ruled it out before any client work.
- What worked
- The limits that decided the question, retention length and how seek interacts with exactly-once delivery, were explicit enough to reject the service without a trial project.
- What got in the way
- A 30-day replay needs retention past 31 days, and an eventually consistent seek would not give a stable starting point for a one-time replay.
