Hi Dattatray,

The approach I described here doesn’t expose the exclusive start and end keys to the client. That was the point — the client shouldn’t be aware of implementation details like that.

As I explained to David, the scheme here is generic and not specific to DynamoDB. It can be applied to other data sources, and it’s all the same to the client since the client just receives an encoded cursor from you and send it back to you when the clients wants to fetch the next page. I have used it with CloudSearch and GrapheneDB at least, and there’s no reason why it can’t be used with other data sources.