Ivan Artemiev

Leaving this here as a reminder: We'll need to revert [these changes](https://github.com/aws-amplify/amplify-js/pull/10020/files#diff-78a8a19706dbd2a4425dd72bdab0502ed7a2cef16365ab7030a5a0588927bf47R1690-R1709) in our canaries after this issue has been resolved.

Hi @sherl0cks, are you still experiencing this behavior in the latest version of the library?

@DiscreteTom thank you for opening this PR. Would you mind adding unit tests for this improvement to [this file](https://github.com/aws-amplify/amplify-js/blob/main/packages/pubsub/__tests__/AWSAppSyncRealTimeProvider.test.ts)?

@BBopanna for large data sets we recommend you utilize indexes based on your data access patterns to avoid having DynamoDB perform scan operations against your entire table. Using indexes will...

For us to better assist you, could you provide a concrete use case you want to implement with AppSync? What kind of application are you building and what are its...

I would prefer that we communicate via GitHub. That way, other customers who have similar questions can benefit from the discussion. Alternatively, feel free to post your questions in the...

@BBopanna, thank you for your patience and for providing the detailed information about your use case. First off, I’d like to point out that the `limit` property does not have...

> So what is the purpose of the limit variable ? to specify a lower limit but not an upper limit ? It's an upper limit. In the example I...

I’m glad to hear the suggestion worked for you! Even if you’ve got 10k+ records generated per day you will accumulate ~4 million records per year. We have customers with...

> So on some day - say 5 years from now - say data has grown to couple of billions and we want to selectively purge, what will be your...