Quote:
Originally Posted by wooorm
|
Nice article.
It is a very complex topic and depends of each application. But local or client storage it is just not possible in all cases. That's why we have SQL, Oracle, MySQL, etc. Because performance, security and limited local space, SQL is usually the way to go. The data is outside, the client reads it via SQL queries or download at will.
You can trick that a bit and move your code to the client side, but again, will depend of what are you trying to accomplish, browser capabilities, etc.
I don't know exactly how this new system works, but the main database is not locally. The client, Safari or Chrome on this case, need to connect and read all your data (book's collection on this example). Later you will decide what to download locally and the additional information that is needed in order to enhance that experience is kept locally too.
Books are usually small in size (not the ones I like though, ironically, SQL books) so moving the balance to the client side, won't hurt on this case I think.