An OAuth authorize URL, callback exchange, and application session each generate potential telemetry; their bill depends on event volume, event size, retention, and indexing. For a media service, a useful first calculation is daily authentication events multiplied by bytes per event and days retained. Consider an explicitly hypothetical workload: 100,000 events per day at 1,000 bytes each, retained for 30 days, produces 3,000,000,000 bytes of raw event payload. This excludes indexes, replicas, and compression. Payload is the dominant term in this simplified calculation; an actual deployment needs measured storage amplification before attributing its bill.
Short answer: implement the authorization URL, callback exchange, and application session as separate security boundaries, then retain compact recovery outcomes instead of authorization payloads. For readers signing into a publication through Google or GitHub, recovery must depend on verified account ownership and another established authentication path.…