3 ms·
How far can we generalize this? If an application has millions of users, can just a little of your server-side load into their browsers can end up saving real m
by andreyf 18y ago
How far can we generalize this? If an application has millions of users, can just a little of your server-side load into their browsers can end up saving real money in server/scaling costs?
More evil-ly, how much computation/storage capacity could Google get by pushing off work/safety advantage of GMail users' machines? Of course, a single computer isn't reliable, but with millions of users, it's a simple matter of failure/redundancy probability. A distributed file system in browers' Gears databases would work just like GFS, but with higher failure rates.
- ionfish 18y agoTo address your first point, GitHub are already doing some of this: they reduced server loads by lazy-loading commit data when cached data isn't available. http://github.com/blog/293-while-you-were-sleeping http://github.com/blog/293-while-you-were-sleeping At work we do a fair amount of client-side form validation. While we have server-side validation too, doing it in the browser as well vastly reduces the number of times invalid inputs make it through to the server and have to be expensively processed. Of course, this creates other problems (making sure the client- and server-side validation routines precisely mirror one another, for example), but for some use-cases it's worth it.