Session
Pick Your Agent's Cache by Its Misses, Not Its Hits
A semantic cache in front of an agent looks fast on every hit, whatever the store. The lookup runs on every question, though, misses included, and the store also bills while nobody asks.
This session runs the same agent caches on two stores, in-memory ElastiCache for Valkey and serverless DynamoDB vector search, and shows how to choose by traffic shape and miss path. Plus the traps: expired items that still come back, and an index that will not create.
What you'll learn:
• A decision rule for the store: traffic shape and miss latency, not hit latency
• A list of platform checks to run before you plan the stack
• The expiry re-check that keeps a serverless cache from serving stale data
• Open-source CDK stacks for both stores, with the agent and dashboard
Outline:
• Why hits all look the same
• The part that does not depend on the store
• In-memory: ElastiCache for Valkey
• Serverless: DynamoDB vector search
• Decision rule and resources
Elizabeth Fuentes Leone
Developer Advocate
San Francisco, California, United States
Links
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top