0

I would appreciate some insights if this is a good/bad design choice.

I have a Dynamodb with an attribute of which all of which have to be fetched for an access pattern.

Instead of doing a parallel scan, would it be OK to write through in elastic cache(Redis set) so that it can looked up instantly?

Shivam Thakur
  • 63
  • 1
  • 11
  • 2
    "Instead of doing a parallel scan, would it be OK to write through in elastic cache(Redis set) so that it can looked up instantly?" Yes, why would that not be OK? – Mark B Jul 15 '22 at 12:56
  • How many items will typically be in this table? – jarmod Jul 15 '22 at 14:12
  • @MarkB I am fairly new to trying caching, couldn't find it to be a common use case so I wasn't sure if this could be an anti pattern – Shivam Thakur Jul 16 '22 at 17:57
  • @jarmod I think initially 10K items each of size 100bytes at max – Shivam Thakur Jul 16 '22 at 17:57
  • 1
    @ShivamThakur it's such a common use case that Amazon built an entire service just to accomplish this common thing, it's called DynamoDB DAX. https://aws.amazon.com/dynamodb/dax/ But depending on the pricing and your specific usage you might be better off using Redis ElastiCache. – Mark B Jul 16 '22 at 18:33
  • @MarkB I see, thanks for your inputs! Btw would Redis open door to many other caching needs compared to DAX setup specifically for dynamoDB – Shivam Thakur Jul 16 '22 at 19:03

0 Answers0