3 ms·
How to multi-cloud. * Start with your architecture, KISS is king. Monolith using as few pieces as you reasonably can. Do you really need two DBs? Do you rea
by BackBlast 4y ago
How to multi-cloud.
* Start with your architecture, KISS is king. Monolith using as few pieces as you reasonably can. Do you really need two DBs? Do you really need a message queue? etc. Trim, cut, remove. Scaling is mostly accomplished by using larger/faster systems.
* Only use the basic services universally available (VM, S3). You need your own provisioning and backup scripts and routines.
* Use your own VPN, nebula has been good for me. Makes your multi cloud infrastructure look like a flat network internally.
* Be very aware of egress costs and how your provider calculates them. Keep intra-cloud comms down. Don't do obviously bad things like host the DB at a different provider than the app server.
You can also mix on-prem/colo with cloud fairly seamlessly if you've built up this way. Cloud makes sense for really small, and for quick changes. Own your hardware when it makes sense. Make the switch when the finances line up with no need to change any software.