Adam Jacob remains optimistic about the future for infrastructure and is building new ideas to make it better.
:link: https://shipit.show/126
So summarizing the “Kubernetes is an anti-platform” statement: it seemed to come down to the fact that K8s is very leaky as an abstraction. I think someone said you build something on it and it’s clear that it’s built on K8s.
Is this a function one of the most popular uses being platform teams building stuff that’s meant host other people’s workloads?
If you’re considering it more as a platform to build a sort of appliance of nodes that’s running predefined workloads and presenting an API/UI that has nothing to do with pods/services/etc does that sidestep the critique (or are there other more platform-ish things to consider)?
Also, I’m asking this having listened to the ep wearing my hoodie that SI sent to their first N beta users because I tried to get it running over a vacation, so I am extremely SI-pilled and ready to believe whatever Adam Jacob tells me. But I am struggling to apply it to the particular use case I’m on right now (and maybe it’s just not a fit and that’s fine).
FWIW I don’t think SI will be a platform to build other platforms. It’s more of the end platform Adam thinks teams should use directly. I think it gets very fuzzy how that works because lots of applications don’t have clear boundaries between app and infrastructure
What I worry about is, how is System Initiative going to avoid the pitfalls of the past graphical programming tools?
These tools that drag and drop boxes on to a canvas and connect them together in a DAG that gets executed by an engine have been around for a while for different customers. Appologies if I'm over simplifying what System Initiative is, but it seems pretty similar to KNIME, Airflow, Kepler, Taverna, Pegasus, VisTrails, just for the DevOps problem instead of what the others target.
Don't get me wrong, I think System Initiative is a really interesting step forward in the DevOps space. What I'm worried about is that (like the other tools) it won't get market penitration to really change things.
Not as on-topic, but I looooved this episode. Felt very "and Friends"
I see System Initiative as a platform to build the platform. Today a lot of teams use Terraform to build their Kubernetes clusters to build their platforms. That's fine but it's just one part of the equation. There are other systems that need to be integrated with where Terraform's design falls short. Think one off APIs that you often shell out to work with in a CI/CD pipeline. In System Initiative you can just write an asset for that and keep it managed along with other assets.
I find the way System Initiative thinks about inputs and outputs to be refreshing. It's easy to see which assets link together and also easy to write "transformation" assets that take outputs from one asset and transform them into inputs for other assets. In a Terraform world that's usually a null_resource
, some complex for
expression, or some shell script to modify variables. I'm sure to some extent System Initiative will be a leaky abstraction but I don't think it will be anywhere near as leaky as Kubernetes.
Hey David - the big difference is that System Initiative isn't built to simplify with a visual workflow. It's built to enable you to build and model whatever you need, and then to build visualizations that make sense. So it's more like the kinds of built in views you would see in something like Unity, and less like KINME (which is cool! but starts from the position that a visual programming environment is the right answer.) We think that'll be the difference maker - it's built for power.
I haven't used K8S myself, but I really enjoyed the episode. I've used Pulumi + AWS for a while. But now I'm trying to move away from cloud solutions, as a personal "back to basics" quest. I'm currently spending time learning basic linux sysadmin and flinging Ansible around with physical hardware.
It's refreshing to hear someone describe K8S as a leaky abstraction. I suppose that since we're knowledge workers, no one wants to be first to say "hey isn't this kinda hard? Should it be this hard?". K8S can do great feats of self-healing and scaling, but it's not trivial (though many proponents say that you just need to do this and so and so. "Basically). :sweat_smile:
Some (all) of the large cloud provider dashboards are ripe for improvement. No wonder, we have businesses like Netlify and Vercel that abstract over the larger vendors. For me, I'm curious about instead of abstracting "upwards", we remove abstractions such as a cloud vendors and find another way to interact with bare metal hardware. Nevertheless, I find that the System Initiative project looks interesting and can provide some real benefits to small and large orgs where diagrams go out of date super quickly. :sparkles:
I listen in my car via .mp3 download and the sound fron Justin and Autumn was very low, while I could hear Adam just fine. I had to almost max the volume on the player and the car. that normally isn't the case, especially when Autumn gets excited about something :lol:
Last updated: Dec 12 2024 at 15:40 UTC