Read performance and caching
Choose caching by freshness needs and prevent language or user data from crossing boundaries.
Different data, different caches
Article and site SDKs only deduplicate in-flight reads. Translations default to 60 seconds; public Portal SSR uses TTL0 and request-local memo. Saving in Administration does not push invalidation to every browser.
Isolate identity per request
Public SSR readers may be shared without user Cookies. Create ServerAuthSDK per request. Translation caches are isolated by namespace and locale; ignore outdated responses during fast switching.
Measure and bound resources
Bound requests, paginate reads, use appropriate thumbnails and distinguish empty data from network failure. Measure first render, requests and memory on the actual deployment instead of advertising untested concurrency, rate limits or availability.