Hacker News new | comments | show | ask | jobs | submit login

What about rolling out updated code? No app, especially web app, is static, so this is a huge deal.

I saw no mention of how this extremely common workflow is handled without taking the app offline, and how this deals with e.g. schema changes...

We handle schema changes very nicely. Our db tool can detect automatically whether a binary and a schema match each other. Most common changes (e.g. field renamings, singletons transformed to lists, etc.) can be handled automatically.

Of course, complete refactorings of subsets of the database may require non-trivial transformation. Opa can't do everything automatically, but it will still check whether the database you obtain at the end of the transformation matches the requirements of your new binary.


If your having several instances load-balanced, you can easily update your site, one instance after another. No server runs mono-process. What do you think?


If it works like this, it's a great feature. But what's happening when in an update the database structures are changed?


There's no easy answer to your question. Although Opa raises warnings when it detects that the databases your accessing/trying to modify have changed, I guess you'd have to think of a migration process anyway.

What is your best practice so far? (and your expectations :p)


Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact