3 ms·
It solved the "rolling upgrade" problem years ago. Did it? For simplicity, http://deis.io http://deis.io should be preferred for modern "deploy-by-buildpack"
by seiji 11y ago
It solved the "rolling upgrade" problem years ago.
Did it?
For simplicity, http://deis.io http://deis.io should be preferred for modern "deploy-by-buildpack" architectures.
- jacques_chester 11y ago> Did it? Strictly, BOSH solved it. But BOSH was originally written for Cloud Foundry, so through the fuzzy lens of distant history it looks the same. In Pivotal we upgrade our public-facing Cloud Foundry installation, Pivotal Web Services, within a day or two of a new CF release being blessed. Typically nobody ever notices. Hundreds to thousands of VMs (I don't know how many we are running now) are upgraded to the most recent version of Cloud Foundry in a few hours and nobody notices. Yeah. It's solved.