3 ms·
d) Deploy them directly to the same bare-metal non-virtual machine, without a VM or container. Yes, you can get cross-app deployment conflicts (packaging, etc)
by pbh101 9y ago
d) Deploy them directly to the same bare-metal non-virtual machine, without a VM or container.
Yes, you can get cross-app deployment conflicts (packaging, etc), and limits your cloud deployment options, but it is definitely another option and has lower overhead than any of the first three.
- raulk 9y agoThat would defeat a major goal of isolation: security. It also creates fragility. What happens if a process is buggy and rallies up to 100% CPU? It affects all others. Although to solve these issues you could use cgroups and namespaces... Aaaand we're back to containers again.
- pbh101 9y agoAgreed on both points. Either I missed your note about isolation on the first read or you edited.
- Veratyr 9y agoOn packaging, can't this be solved by static linking or something like Nix?