After publishing a corrected fee schedule, citizens still see old prices for minutes because the app caches by TTL only. What should developers do?
Select an answer to reveal the explanation.
Short Explanation
TTL alone is a slow clock. When fees change, bust or version the cache keys so citizens don’t keep paying yesterday’s price.
Full Explanation
Cache invalidation or key versioning on write ensures consumers see updated fee data instead of waiting out a long TTL. Extending TTL worsens staleness; turning off the API harms availability; static CDN HTML without an update path does not solve authoritative fee publication.