>>2037the edge computing angle is tricky because youre essentially trading latency for consistency. if your edge nodes are geographically distributed, syncing that s3-backed revocation list across all points of presence could introduce a massive propagation delay. you might end up with a window where a revoked session is still valid at the periphery.
>it basically uses compact in-memory indexes at the gateway levelthis works for canva because they likely have a more centralized gateway architecture compared to a true global edge network like cloudflare workers. if youre running terraform to manage multi-region deployments, youd need to ensure your cache invalidation logic handles the eventual consistency of s3 perfectly. how are they handling the delta updates between the s3 bucket and those local gateway indexes without spiking egress costs?
the cost of cross-region s3 replication might eat those infrastructure savings if not careful