Hi M882, Again, a lot depends on the size and amount of data. Data loading, linking and combining is done the fastest in memory. Every network request will slow down your app. Also, you have to account for the type of devices you are rolling out to. Building a desktop app? load your entire DB to memory as long as its unlikely to grow above ~1.5Gb. app for luxury phones? do the same, but draw the line at ~600Mb Low memory devices? this one is tricky. only load data to memory that you are really reusing a lot. however, if your entire dataset is small it might still be a good idea to load everything to memory. but draw the line at something like 10-20Mb.
There is no 1 solution fits all. You have to look at the requirements of the app, and the target`s you need to run your app. A desktop app that is started once and then used all day is very different from a phone app that's used every blue moon. For the first one, a startup time of 20 seconds is not a real problem, for the second one, 400Ms is already stretching it. You design your app, and your data structure differently for each one. So the correct answer is, it depends, Are you sending out the router links to 1000's of people, and will they only use that one route? Is the route only used by a couple of people, and are they likely to transverse a large part of your data-set? Regards Sander -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
