I'm using queries that can return many documents.
In my UI I would like to split it into "pages" so each page contains a manageable amount of documents.
I read the documentation of scrolling, but if I understand correctly, it will not be sufficient as only the newest scrollId can be used. So if my user wants to view an earlier page it will not be valid. In addition, even if it was valid, I would need to cache all scrollIds in my application.
I also saw the slice option - which sounds more like what I'm trying to achieve - so is this my solution? Should I use a big scroll to hold all the query results and then slice it? I understand there might also be a performance impact with slicing.