101 karma · joined August 31, 2015
As you point out, there are definitely trade offs with choosing Lavastone instead of a SQL database. For instance you can’t easily share concurrent read/write access to the same Lavastone data with multiple processes. However, you can copy a fixed Lavastone data store (ie the underlying LevelDB store) and distribute it to multiple server nodes. That’s how we used it anyways!
https://en.wikipedia.org/wiki/Post%27s_lattice
Given several logic gates, if their most recent common ancestor in the lattice is the clone of all boolean functions, then that set is universal. This provides a convenient prescription for deciding universality for a new k-input gate.
-->source?
1 The container would need to be privileged so that it could run a docker daemon and containers (sidomo processes) within itself.
2 (the "right" way) Use the host's docker daemon from within the first container by binding the docker.sock to the child container. The first container can start and stop others that run next to it, instead of inside it. This way there's no recursion, and no containers need root privileges.
Our Container class is built so that if you use the `with` statement, container termination is handled automatically even if there's a program fault.