Welcome to the discussion about this lecture. Here you can ask questions or post feedback about this specific lecture.
Why are clients dumb? Bringing some tasks to the client can relieve the server from different tasks (filtering is a big example) so that it is not saturated. Also Google Maps has an offline mode where you can find the route between two cities if you downloaded the map before.
I would think it depends on the app. A simple use-case for a mapping app is that it can be used offline. In which case, the data in the client is throw-away (glossing over the details, of course). But if the app were more robust and tracked where the user travelled (even if offline), there would have to be some kind of function that synchronizes the data from the client with the centralized servers. In the end, the centralized servers need to ultimately house and control everything. Not sure if this example helps, but I hope it does.
Clients are dumb in centralized infrastructures because they don’t perform the mathematical and logical tasks performed by servers.
For your map example, there is so much to data the client can hold. Once it gets to that threshold or when the clients holding session expires, it ceases to hold any information. A good example is Youtube save for offline videos, they only stay say about 30 days and you would need to reconnect to the server to download new packets for those video before you can watch them.
Even at some point when a decision was taken at the server level to restrict users from saving videos offline except they join the YouTube members subscription plan, the client had no option that to give up those videos.
And even when it holds information, it is still dumb because it won’t still be dynamic like the server would.
Very Nice! Thank you, Ivan!
Topic well explained! I think Centralized IT Infrastructure is the Traditional Way storing data on the internet. Decentralized IT Infrastructure is definitely the future.