3 ms·
I went the opposite direction, 1 vm per service. It's much easier to secure, backup, restore thanks to full isolation.
by js4ever 5y ago
I went the opposite direction, 1 vm per service. It's much easier to secure, backup, restore thanks to full isolation.
- sdze 5y agoI hope you don't use the VM snapshotting feature as backup method? I had problems when running a database service on it for obvious reasons.
- js4ever 5y agoNop indeed, I use the native backup tool to create a dump then use borg to save the backup in a remote location
- fersarr 5y agoMe too. Yesterday I was trying to add a second app (3 docker-compose services) to one of my 5$/mo droplets and it started impacting and slowing down the other app. Debugging was harder too and could affect both... Perhaps at some point I'll try it again.
- southerntofu 5y agoSounds like your server may have been swapping? Disk IO is notoriously bad on most VPS so make sure to disable swap and setup oomkiller. In the case of a small VPS, containerization overhead is also not negligible: you may consider to setup everything natively (to your VM) to counteract that.
- fersarr 5y agoYea, that makes sense! Ty
- candiddevmike 5y agoYou should look into systemd-nspawn, VM experience without the overhead.
- k8sToGo 5y agoBut that bloats your backups like crazy. Much better to use something like Ansible to setup the VMs and then just backup the data.
- rubatuga 5y agoTrue about the backups. I'm thinking once I upgrade to 22.04, I'll be able to use virtio-fs for better efficiency (+ actual dedup!).