3 ms·
What options are there for syncing flux stores on the server and client? I ask this because the increasing move towards microservices seems to suggest that "jo
by malandrew 12y ago
What options are there for syncing flux stores on the server and client?
I ask this because the increasing move towards microservices seems to suggest that "joins" are going to start taking place on the client via waitFor.
For example, if I get model A and it depends on Models B, C and D. I don't want to have to wait for the client to fetch model A before it knows it needs to fetch models, B, C and D. Ideally, as model A passes through the server side store layer, it already starts fetching models B, C and D so it has those ready to serve to client, (or better yet it anticipates that the client is going to want B, C and D and eagerly sends that data to the client).
- collyw 12y agoThat sounds like a problem of pushing too much processing to the client side.
- collyw 12y agoA downvote for pointing that out. Can someone explain why I would want to do joins on the client side, when there is mature, well tested, well understood technology for doing joins on the server side? All the data is going to be on the server, so no danger of loosing a connection.
- deleted 12y ago[deleted]
- colinramsay 12y agoI think a real-world example might help to describe what you mean. Perhaps you could normalise the data in a way (on the server-side) that would remove the need for this setup?