• @ceremcem, I see where you're going.

    1. Create backup of current working code
    2. Deploy new code
    3. Wait for heartbeat (and may be other signs of 'positive, successful' life of new code
      4-Y. If heartbeat arrives: keep going with new code
      5-N. If heartbeat fails to arrive: back-out from new code and re-inbstate previous version

    I'm thinking of a VM concept where there is a Host and a Guest... the Host is rock solid, always there and a minimal (communiction) environment to host Guests... and the Guests are the actual applications.

About

Avatar for allObjects @allObjects started