4 ms·
How would this handle external state? I realize in general that's an impossible task, but specifically I'm thinking of something like a database. Is there a way
by defen 6y ago
How would this handle external state? I realize in general that's an impossible task, but specifically I'm thinking of something like a database. Is there a way for each "server" to get a private copy of the database? Otherwise it seems like if I create a non-backwards-compatible migration (let's say I drop a table that's no longer necessary) I could break servers that were spawned for other commits.
- colinchartier 6y agoGlad you asked! If you do the Django tutorial after clicking "try now", you can see an example of a postgres database that gets set up for every run. Since we give full VMs instead of just containers, you can keep the database running in the background. Because we do memory snapshotting, you could turn a 5 minute database start + migrate + populate into a 1 second "restore from memory snapshot"
- ignoramous 6y ago> Since we give full VMs instead of just containers, you can keep the database running in the background. Interesting contrast to flockport that runs multiple processes in a LXC [0] (treats it like a lightweight VM). [0] https://news.ycombinator.com/item?id=17478736 https://news.ycombinator.com/item?id=17478736