Let's discuss - how do you fetch your tabular data?
Do you load it initially and then only do client side processing?
How do you sort - local or remote sorting? What about filtering?
Do you use grouping or pivoting - and if so, does it happen in the browser?
Keen to find out how other people do it 🤔
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (7)
I always tend to paginate with filters in backend and render on fronted. I know that server side rendering were recovering strength the last years but I prefer to pay less for the server and let the hard job for the client.
If I need SEO I'll do SSR (with Next JS probably) then prepare a web service to provide the data with filtering, ordering, pagination and so, that's to avoid huge network loads that will hurt core web vitals at some point.
If it's an internal business app which does not require SEO I can extend the items per page much more adding loaders and so and avoiding SSR.
I use a React table library.
@andrewbaisden Do you mind sharing what table component you're using?
We're building Infinite Table and are wondering which data-loading strategies people need most. We think we've covered most of the use-cases, with both client-side and server-side integrations, for all functionality we offer in the table - filtering, sorting, aggregation and even pivoting. For example, see our server-side pivoting support which allows you to pivot data on the server and basically the pivot table can aggregate millions of data points - it's all bound to what fits on the server and not limited to client-side pivoting anymore.
Also react query is a very popular solution for React apps, so we have a demo integrating it for live pagination
I'm using tanstack.com/table/v8 they made tanstack.com/query/v4. The same company that made react query but I think they have rebranded to tanstack?
🎉 TanstackTable is a great library and integrating it with react-query (now also tanstack query) is a perfect match! I'm also using react-query and absolutely love it! Data-fetching is only trivial at first sight, but there are so many edge-cases and things that can go wrong - and react-query is perfect for doing the heavy lifting of handling all of those for us. Great combo!
i think it's really depends of the amount of data.
I usually don't worry to much when there is not that much data and do most of processign in the front end.
When data get's big i have mostly rely on graphql. ( that's for the static generated websites ). But really like to hear more about alternatives and/or better ways dealing with it.