M
M
mr_drinkens2017-06-23 13:34:53
React
mr_drinkens, 2017-06-23 13:34:53

Redux with a large amount of data in the Store?

Hello.
Wondering if my approach is correct. Who came across, tell me)
The application is like "Trello" or "kanban-approach". (boards, lists, tasks, attachments, and so on).
Current version: when a user logs in, I load all the data from the server (boards, lists and tasks, files, and so on), and already on the client I filter them, depending on the user's choice. Roughly speaking, store stands for a certain database on the client, and filter works like "select ... from ... where" - if we make an analogy with a server database.
With small amounts of data, everything works well (a couple of boards, 15 lists, and 50 tasks). But how will this scheme behave when the amount of data increases? When there are about 500 tasks (figuratively imagine,
And in general, is the approach correct when, with any user "click" (if it is not related to an update), I drag the necessary data by filtering (instead of "pulling" the data from the server via the API)?
Thanks to.

Answer the question

In order to leave comments, you need to log in

1 answer(s)
N
Nikita Gushchin, 2017-06-23
@mr_drinkens

The simplest is to generate 500-1000-whatever tasks and see what happens to your system.
Generally speaking, I think this is a bad decision in most cases. Especially if there are large amounts of data...
And if the user does not see most of this data at all, then why? In my memory, such a model was used in an online store where there were not many goods, but this allowed users to use the resource offline.
Carry out testing (imitation of the worst scenario) and by the results you will already see whether this solution is suitable or not

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question