5 ms·

Kubernetes is a very flexible way to host microservices today, which also means it takes a lot of effort to manage and keep running in a workflow. And while we

Kubernetes is a very flexible way to host microservices today, which also means it takes a lot of effort to manage and keep running in a workflow. And while we needed something like Kubernetes this past decade to grow microservice architecture en mass, many of things that Kubernetes does right now will be abstracted away over time in a way that maintains much of that same flexibility. In that respect, yes, Kubernetes is important for the future of data platforms - but as a stepping stone (an angle that was absent in the author's post).

ayanb 5y ago
Curious - could you elaborate how you think this abstraction will happen over time?
- jasoneckert 5y ago
  I think that'd be near impossible to speculate on. There could be hundreds of different ways it could evolve that way, including ways that involve frameworks that haven't been invented yet.
tjr225 5y ago
You can spin up a managed k8s cluster that more or less “just works” with about 6 lines of cdk/pulumi/terraform. Need to update your cluster? Rerun cdk/pulumi/terraform.
vlunkr 5y ago
> Kubernetes is a very flexible way to host microservices today, which also means it takes a lot of effort to manage and keep running in a workflow. I don't see how the second point necessarily follows from the first.
- jasoneckert 5y ago
  Ah - by flexibility, I meant to imply that there are thousands of different ways to host microservices, based on the needs and architecture of your Web app. And because of this, there isn't a set of standard tools and practices that can work for all Web apps, and when things change it often requires big workflow changes as well. In other words, for anything other than a simple Web app (which could be workflowed with GitOps) you have to have a good SRE to keep things running with Kubernetes ;-)
StreamBright 5y ago
> Kubernetes is a very flexible way to host microservices today So are a gazillion other solutions that do no claim that they are essential for the future of data platforms.

ayanb 5y ago

Curious - could you elaborate how you think this abstraction will happen over time?

jasoneckert 5y ago
I think that'd be near impossible to speculate on. There could be hundreds of different ways it could evolve that way, including ways that involve frameworks that haven't been invented yet.

tjr225 5y ago

You can spin up a managed k8s cluster that more or less “just works” with about 6 lines of cdk/pulumi/terraform. Need to update your cluster? Rerun cdk/pulumi/terraform.

vlunkr 5y ago

> Kubernetes is a very flexible way to host microservices today, which also means it takes a lot of effort to manage and keep running in a workflow. I don't see how the second point necessarily follows from the first.

jasoneckert 5y ago
Ah - by flexibility, I meant to imply that there are thousands of different ways to host microservices, based on the needs and architecture of your Web app. And because of this, there isn't a set of standard tools and practices that can work for all Web apps, and when things change it often requires big workflow changes as well. In other words, for anything other than a simple Web app (which could be workflowed with GitOps) you have to have a good SRE to keep things running with Kubernetes ;-)

StreamBright 5y ago

> Kubernetes is a very flexible way to host microservices today So are a gazillion other solutions that do no claim that they are essential for the future of data platforms.