troubleshooting Question

when to implement server side pagination

Avatar of Crazy Horse
Crazy HorseFlag for South Africa asked on
Node.jsReactDatabasesJavaScriptREST
5 Comments1 Solution13 ViewsLast Modified:
I have implemented a search and pagination in React. The search is basically using .filter. The data is coming from MongoDB/Node.js but there is no pagination on the backend.
The reason I like doing it purely on the frontend is because it is really fast but it wouldn't be good to load 1000's of records at once from the api I would imagine and sending only say 10 records at a time from the backend would be better. But then I would lose the speed and couldn't use filter on the search anymore for all records because I have limited data and I would need to send the search query to the server. (I assume!)
So, my question is if I am anticipating about 30 records per month per user to be added then after 12 months, a user would be loading 360 records at once which they could then 'search' and go through the pagination all on the client side.

What is the rough number of records where this would become problematic and implementing pagination on the backend would be necessary? I am trying to determine if I can leave it as is or need to sort of future proof the application by implementing server side pagination.
ASKER CERTIFIED SOLUTION
Join our community to see this answer!
Unlock 1 Answer and 5 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 5 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros