3 ms·

I guess most of my apps have persistent data.

• smt88 4y ago
  Every useful app has persistent data. It sounds like you have a design problem, though. If you're treating application servers like cattle, then none of them should have persistent data (except caching that's disposable). There are fire-drill days that require deployments, so downtime incurred when updating your application code is unacceptable. To solve this, put your persistent data on a separate server and store it in a proper database (Postgres, for example). Postgres never needs emergency updates, so the downtime for those (infrequent) updates can be pushed to non-peak hours.
  • conradfr 4y ago
    I would maybe do all that if it was for more than side-projects that can tolerate 5-10 seconds of downtime when deployed :)
    • smt88 4y ago
      That's fine, I wouldn't tell you otherwise. You just complained about a missing feature that isn't actually missing if you use the service properly and treat servers like cattle.
      • conradfr 4y ago
        Well yes, some containers only read the persistent data so if those could have zero-downtime as there's no risk of data corruption it would be great, but that option is not offered to me.