| > Serverless implies that the management of the underlying infrastructure is owned wholy by a third party, This is an AWS talking point, which they push relentlessly because it suits their purposes. The idea that developers "I don't care about servers" implies or doesn't imply anything about the legal ownership of servers doesn't, by any necessity, actually follow, unless your name is Bezos. > You still need to water and feed a Pivotal/K8s platform, and those things are awful to run. I have run them single-handedly in my day job at Pivotal. We have customers who run platforms for thousands of developers with < 10 operators. > By this stage, you end up having to re-write those parts of the json/yaml/terraform to handle deployments into other clouds ANYWAY. So what's the benefit again? Or you could use BOSH today and Kubernetes in ~-12 years as its ecosystem firms up. Or both as fits your workloads. Pivotal is ready for both and to help you handle your workloads. > You run your own logging, storage, networking, database and analytics services inside the K8s which defeats the entire point of being in the cloud in the first place. Why? > Just use the native FaaS/Data/Analytics. I actually half agree with you. Cloud portability is to me not the primary selling pitch of the software Pivotal works on. It's a benefit, one which many of our customers see as essential. But to me the point is: can I just write some damn code? That's what I want to achieve. Solve the damn problem, rather than shaving yaks all the damn day. The portability thing is just a means to that end, not an end in itself. Disclosure: I work for Pivotal. |