Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 5
    Good points. I would also suggest the case of caching. It might be tempting to push a very expensive calculation to the client, but if the same calculation would be performed many times by different users, it may make more sense to do it once on the server then serve the cached result subsequently, especially if each request would have an element of overhead for the server in gathering the basic ingredients, which could be reduced if a prepared and stored result was served. Commented Nov 5, 2019 at 16:02
  • I apologize asking this year's later, but I found this simple and easy to understand explanation and wonder if it applies to my case, too. I fetch data (calendar records) and my weekly view needs the data in a different way than my month view. Do you think I should transform one data into the other (quite possible, but requires a series of array transformations) or if I should fetch it from the server? I'd go for the latter, but if my application is supposed to work offline, the former would be better, right? Commented Dec 15, 2022 at 2:11
  • 1
    @Igor, if you need to support off-line operation, there is only 1 way to get it to work. Otherwise, my answer would apply to you as well. Commented Dec 15, 2022 at 10:41