3 ms·
Colocation isn’t a binary on-or-off thing. As a crappy example, Kubernetes pods maintain the invariant that all containers within a pod exist on the same Kubern
by __blockcipher__ 6y ago
Colocation isn’t a binary on-or-off thing. As a crappy example, Kubernetes pods maintain the invariant that all containers within a pod exist on the same Kubernetes node. So you can avoid the most egregious waste of resources/time that comes from having no collocation.
To your point, when talking to your db or [insert shared infra here], then you may want to thinking about real collocation. But it very much depends on your application’s needs - and remember that cloud providers can offer guarantees about which AZ or region you’re in.
- vinceguidry 6y agoI did mean real colo. If I ever run a serious public-facing website, I have a colo facility picked out, just drive down there with my custom server. Only a few hundred bucks a month to serve data to a CDN, along with whatever services I want to directly expose. With the magic of VPN, I can put my colo box on the same k8s cluster as the rest of my home stuff, in case I want to live dangerously.