6 ms·
If you're really trying to serve the outside world, then you want colocation. Cloud providers are way more expensive.
by vinceguidry 6y ago
If you're really trying to serve the outside world, then you want colocation. Cloud providers are way more expensive.
- emodendroket 6y agoDepends on what you’re doing and at what scale. Especially for smaller orgs it’s really hard to duplicate the level of service the big boys can provide yourself.
- vinceguidry 6y agoIt's certainly not for everybody.
- vinceguidry 6y agoI just thought of another reason. Rolling your own cluster forces you to understand what Kubernetes is at a basic level. If you never get that experience, and just roll with cloud services, you aren't really getting that and will tend to get mystified by errors which, you'd have a much better idea of where they're at if you've rolled your own. Kubernetes is very complicated, but the complexity can be managed if you approach it from the bottom up. Using a cloud service robs you of that ability.
- emodendroket 6y agoThe pitch for Kubernetes is kind of supposed to be “infrastructure as a service,” isn’t it?
- vinceguidry 6y agoNo, that's the pitch that Amazon / Google makes. Kubernetes has a much more complicated value proposition that you have to grasp the hiring dynamics of Google to really understand. Google hires really smart people but smarts isn't necessarily skills. So it builds tech to leverage that workforce. Other companies hire skilled people that aren't necessarily super-smart, because super-smart people can make a lot more money at Google. So other companies use Google / Amazon, they don't really care what underlying techs it uses, so long as they know they'll be able to hire people with the skills. If you're rolling your own Kubernetes, you're putting your faith in your own smarts, because you're largely on your own. K8s rewards a certain kind of developer, and badly punishes someone thinking running their own k8s is going to be as seamless a process as consuming GCP resources.
- emodendroket 6y agoYeah but that’s my point, not everyone needs to actually set it up. The intent is for most to just be users and concern themselves with editing yml files to bring up their services.
- Shared404 6y ago> Kubernetes is very complicated, but the complexity can be managed if you approach it from the bottom up. s/Kubernetes/Computers
- __blockcipher__ 6y agoColocation 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.