>>>It almost sounds like a form of resilient design (i.e. progressive enhancement) if you think about it — the cloud as an optional, layered enhancement of your application. Now that’s a paradigm shift!
This is literally what was pioneered by Lotus Notes 32 years ago. When everything was local, their rich-content databases could work just fine locally and also replicate on any desired schedule with other copies of the same databases/apps. The model was explicitly Seldom-Connected, so you could run stand-alone in a remote location for weeks and send/receive updates whenever you got to a phone line, or could have it collecting/distributing updates every N seconds on a persistent connection.
A vastly superior model to everything I've seen since, and it is too bad that they, and especially IBM blew it with the weird programmability models and corporate-extract-every-dollar approach.
Acting as if this is a somehow new concept is just a display of cluelessness, but it is good to see good concepts getting some attention (again).
This is literally what was pioneered by Lotus Notes 32 years ago. When everything was local, their rich-content databases could work just fine locally and also replicate on any desired schedule with other copies of the same databases/apps. The model was explicitly Seldom-Connected, so you could run stand-alone in a remote location for weeks and send/receive updates whenever you got to a phone line, or could have it collecting/distributing updates every N seconds on a persistent connection.
A vastly superior model to everything I've seen since, and it is too bad that they, and especially IBM blew it with the weird programmability models and corporate-extract-every-dollar approach.
Acting as if this is a somehow new concept is just a display of cluelessness, but it is good to see good concepts getting some attention (again).