Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do we need support for "atomic", or "blue green" deployments? #269

Open
jbardin opened this issue Sep 25, 2015 · 1 comment
Open

Do we need support for "atomic", or "blue green" deployments? #269

jbardin opened this issue Sep 25, 2015 · 1 comment

Comments

@jbardin
Copy link
Contributor

jbardin commented Sep 25, 2015

We currently roll out deployments as fast as we can through the cluster, but we have no way of synchronizing those events, which leads to a mix of versions running for a period of time. This hasn't caused any problems yet, but it seems that at some point an incompatibility between version N and version N+1 will cause a problem.

@joeshaw
Copy link
Contributor

joeshaw commented Sep 25, 2015

The ability to do an atomic switchover would be nice, but the compatibility issues we tend to have surround the database schema. For those it'd almost be better to queue up and block incoming requests and route them to only new app instances once that migration happens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants