How DynamoDb console maintains pagination along with filtering

Question

Suppose I have 110 records and I filter upon status for the first page two calls are made the first calls scans 25 items and after filter it receives 20 matching items , it uses the id of the 25th item as last evulated key and passes to second call as exclusive start key , the second call again scans 25 items recives 19 matching records , now note : this two calls were both made for page 1 only so total record is 20+19=39 but in UI it displays only 25 , then in next page it first displays the 14 records than the response from the third api call and so it goes like this

Questions :

1. Where does it store that 14 records?
2. Is it feasible to try and do this in my service

Right now i have loop that calls similarly but it returns 39 records and they are shown in UI , I want to show only 25

• luk2302: That is just a manual client side pagination, you can store the "extra" items you fetched wherever (local storage, cookies, disk, variable, ...), it literally does not matter. The UI pagination is simply decoupled from the API pagination. And sure, you can just replicate that yourself if you want to.
• Khushi Bansal: is this the ideal solution or is there any other approach

Answer 1

The console uses a Cloudscape table component, where it limits the view to 25. Then the next page, just shows the additional items in the component. So all items were already fetched, changing pages on the UI is not calling the API again.

DynamoDB page != UI page

• Khushi Bansal: thankyou so much for this info , should I do the same or do you have any other approach that I can try . Thanks in advance.
• Leeroy Hannigan: This is typically how users would implement pagination. If your requirements are satisfied with this approach then I would go for it