I think main advantage of DDB is being serverless. Adding a server-based layer on top of it doesn't make sense to me. I have a theory it would be better to hav

I think main advantage of DDB is being serverless. Adding a server-based layer on top of it doesn't make sense to me. I have a theory it would be better to have multiple table-replicas for read access. At application level, you randomize access to those tables according to your read scale needs. Use main table streams and lambda to keep replicas in sync. Depending on your traffic, this might end more expensive than DAX, but you remain fully serverless, using the exact same technology model, and have control over the consistency model. Haven't had the chance to test this in practice, though.