Scroller — Cache & Fallback Flow

How wiki, wikivoyage, and images degrade gracefully when upstream is unavailable

REQUEST CACHE LAYER ORIGIN /wiki getWiki(100) /wikivoyage getWikiVoyage(100) /images getImageItems() /amazon getAmazonItems() unstable_cache 10 min TTL · shared across lambdas key: wiki-bucket-v4-iter MongoDB AIDB.wiki · 67,856 articles fallback when Supabase empty S3 signed URLs com27 · ListObjectsV2 HeadObject on detail only MongoDB AzDB.MAIN + AmazonDB fallback: Google Sheet CSV Wikipedia Action API generator=random · 50/call _iter param defeats dedup WikiVoyage Action API generator=allpages · bulk cached 67,856 articles in AIDB.wiki AWS S3 com27 eu-west-2 · BucketOwnerEnforced PublicReadScroller policy Amazon ZGBS 34 categories · tag fs08-21 withAmazonTag() normaliser cache miss → origin · hit → cached response in <1ms