Pagination or no pagination
Hi i cant decide to whether implementing pagination or not.
I understands that pagination serves the client a subset of data to offload the computing of the backend. While this is great when x amount of client are request data from a table. The problem lies when they need to do the filtering, the filtering only happens on the subset instead of on the whole table.
So if the table consist of 1000 records and the subset is 10, filtering only happens on the 10 records.
Do i have to implement a call to the backend for each every filtering that being applied? does this just lead to more database calls?
So what is best serving the client a bigger set of data so the filtering can happens client-side
or do the filtering on the backend side and ends up with more calls to the backend
Thanks in advance
I understands that pagination serves the client a subset of data to offload the computing of the backend. While this is great when x amount of client are request data from a table. The problem lies when they need to do the filtering, the filtering only happens on the subset instead of on the whole table.
So if the table consist of 1000 records and the subset is 10, filtering only happens on the 10 records.
Do i have to implement a call to the backend for each every filtering that being applied? does this just lead to more database calls?
So what is best serving the client a bigger set of data so the filtering can happens client-side
or do the filtering on the backend side and ends up with more calls to the backend
Thanks in advance
