Currently, frontend fetches the list of all experiments from the backend and the pagination is implemented as part of the frontend itself. This may lead to performance issues once the number of experiments returned grows to a significant number. What would help is to ensure that our experiments table view can display any number of experiments is a backend-driver pagination.
In this solution:
frontend would tell the backend the size of the page and the page number
frontend would not be able to implement operations such as sorting/filtering/searching - all of them would need to be moved to backend.
Complexity [S/M/L]: M
Wireframes, Mockups, or Screenshots (if applicable)
Description
Currently, frontend fetches the list of all experiments from the backend and the pagination is implemented as part of the frontend itself. This may lead to performance issues once the number of experiments returned grows to a significant number. What would help is to ensure that our experiments table view can display any number of experiments is a backend-driver pagination.
In this solution:
Complexity [S/M/L]: M
Wireframes, Mockups, or Screenshots (if applicable)