3 ms·
Indeed. Or anything else on https://en.m.wikipedia.org/wiki/Orchestration_%28computing%29 https://en.m.wikipedia.org/wiki/Orchestration_%28computing%2.... To wr
by nailer 7y ago
Indeed. Or anything else on https://en.m.wikipedia.org/wiki/Orchestration_%28computing%29 https://en.m.wikipedia.org/wiki/Orchestration_%28computing%2.... To write as if Kubernetes is required to orchestrate computing (particularly in an environment where other containment tech is already available) shows unfamiliarity with a huge body of work from the last two decades.
- scarface74 7y agoI wouldn’t call CloudFormation or Terraform “Orchestration” despite what Wikipedia says. Neither adjust resources dynamically based on health checks, workload, a certain time or based on resources available on the underlying VM. I don’t know the other tools but it makes me doubt the entire Wikipedia article based on what I know.
- nailer 7y agoIn cloud formation you'd make an autoscale group to handle dynamic adjustment of EC2 resources (ie, Xen VMs) or make Lambdas which are started and terminated as needed (is, Firecracker VMs).
- scarface74 7y agoCloudFormation isn’t doing the orchestration though. The orchestration is being done by the load balancer, APIGW, CloudWatch alarms, or whatever AWS uses to route events and trigger lambdas.
- nailer 7y agoYes, agreed. You're creating a resource to do the orchestration built with particular rules, rather than creating and applying those rules directly. I'm not sure the distinction is significant though - ultimately the rules in CF determine your scale-up/scale-down behaviour, directly or indirectly. Perhaps more to the point of the other poster: autoscale groups existed pre-containers and microVMs exist after, orchestration being orthogonal to containment tech.
- scarface74 7y agoSort of playing devils advocate. But lambdas are containers. Instead of a Docker container, you have a zip file. Now, you can even have up to 5 layers in your lambda and it works even more like a building a Docker container.
- nailer 7y ago> But lambdas are containers. Nope. Technically they're MicroVMs, based on KVM not LXC. They're an isolation tech but containers aren't the only isolation tech (which is really the whole point of this discussion). https://firecracker-microvm.github.io/ https://firecracker-microvm.github.io/ Firecracker runs on Intel CPUs. 2 layers. No probs with you playing devil's advocate, you're a lot more polite than the other guy (who seems to have quietened down since pre-and-post LXC orchestration was pointed out to him).