3 ms·
>If there's state in that virtual machine, it's probably either stored on the physical host or in a SAN I think the point is to write your application in a way
by treis 7y ago
>If there's state in that virtual machine, it's probably either stored on the physical host or in a SAN
I think the point is to write your application in a way that there's not state in the VM. My VMs are disposable and in fact the way I do deployments is to spin up a new VM in DO and then assign it the floating IP for production. If things go haywire I can easily swap back the IP address to the known good VM.
- dijit 7y agoAre you using managed databases then?
- treis 7y agoI am. Mostly for the backup and other DB administration that comes with it. Also use Spaces (DO's S3 equivalent) for any assets that aren't packaged with the code like user uploads.
- aitchnyu 7y agoFuture wish: all VPSes have managed databases, object hosting and centralized logs as standard so as not to rely on local disk at all. There is a streaming backup protocol, which allows any database and queue vendors to stream to any location, and acts as a peer for fully synchronous replication. If your DO Postgres, Kafka and Mongo instances are killed, you have a Bakstream cluster in Linode which lost no data and allows you to restore in Vultr.