Best way to do low-latency lookups for ML model prediction caching?

Question

I'd like to increase AWS posture on ML model prediction caching. Let's say we want to serve a lookup table upstream of a REST API that contains past predictions, and look it up at every prediction to avoid re-running through the model when a given input-output pair has already been computed. It's ok to wait several minutes between cache updates and typical TTL could be between minutes and days. What is the best way to do that in AWS?

1. Use the caching functionality of API GW?
 1. Use a warm Lambda@Edge that locally has a lookup file with past predictions? 
 1. Use DAX or Elasticache upstream of the model call? Is there a way to have DAX or Elasticache live at the edge?

Achraf Souk · Accepted Answer

You can use CloudFront in front of your API to cache HTTP responses according to the Cache-Control header sent by your origin. Please note that this would only work for GET/HEAD HTTP requests.

Best way to do low-latency lookups for ML model prediction caching?

Add your answer

Relevant content