|
|
|
|
|
|
by jpswade
3055 days ago
|
|
|
Kubernetes takes you to serverless, where you don't care about the hardware. The next shift is what I've called "stackless" - why do you even care what platform it runs on? All you want to be able to do is have your application run somewhere. Kubernetes goes some way towards that, but there's another abstraction layer needed. Similar to how Docker was an abstraction further to Kubernetes and away from Vagrant. This is something I wrote about this not long ago[1]. 1. https://wade.be/development/sysadmin/2016/11/17/stackless.ht... |
|
|
Serverless isn't a good name - but it doesn't stand for "don't care about the hardware". Devs are already not caring about hardware anymore since VMs.
What serverless removes is the abstraction level of a server/vm/container.
A simple example is scaling your stateless components. In a serverless FaaS, functions are scaled for you. You don't have to do anything to handle a peak in web traffic. You don't have to do anything to handle a peak of msgs in your MQ.
In k8s, you still have to go and fumble around with CPU/memory limits and better get it right. k8s also doesn't scale your containers based on the msgs in your MQ out of the box. You have to build and run that service yourself (or ask GCP to whitelist you should you be running their MQ https://cloud.google.com/compute/docs/autoscaler/scaling-que... ). AWS Lambda had that since 2015...