Exceptional examples. But what I miss here is instructions how to do it actually well? Instructions how to * upgrade server-applications quickly without user

Exceptional examples. But what I miss here is instructions how to do it actually well? Instructions how to * upgrade server-applications quickly without user interruption * to create autonomic applications on client-side * how to change data models in the background Desktop mail-client like Evolution or "git --everything-is-local" are good examples. They work autonomic and can sync with servers anytime. The examples of the author are awkward exceptions. Real world ones are available. For example Garmin Connect or Google Mail. Garmin Connect cannot do anything autonomic and we've seen an outage last year over a complete week. The same for Google Mail, it cannot download all mails in an mailbox. On a mobile device with 128 GB disk space. You see the irony? A mobile device which will suffer concnetion loss often which a big disk? Leets look at K-9 mail or Evolution: Download all? YES! Sync when possible? YES! That is my recommendation. Make your local application autnomic and use servers to sync when possible. Of course that cost time in development. And it should - reliability costs. Making a server un-failable isn't possible. By the way, I'm interested in quick and better migration best practices.