#25 Why VMware Tanzu if there are soooo many open source choices?

What is it? I know this is super hard to say, you know, like an elevator pitch, but if you can do it in a couple words. Briefly, Tanzu is like the name we apply to all the stuff, most all the stuff we have in VMware that helps out your application developer stack. So if you're an organization that writes and runs your own software, that's what the Tanzu suite handles. So there's your very small explanation now. I love it, I love it. So that is the question following, right? So the question is, why do we need Tanzu if there is Kubernetes, you know, like a pure one, like open source, like this native one, Vanilla. Tak, tak, tak, więc Kubernetes jest tylko jedną częścią całego stacku, prawda? Więc patrząc na Kubernetes samemu, powiem tylko generalnie o tym, prawda?

Rzecz, dlaczego potrzebujesz dystro Kubernetes, chociaż to nie jest naprawdę terminologia, którą ludzie używają, ale czy potrzebujesz dystro, aby je uruchomić samemu, czy chcesz je uruchomić w publicznym cloudzie, ktoś to uruchomi dla Ciebie, jest, mówię, to te same powody, dlaczego chcesz, tak, dystro Linux. Or whatever. It's just like you could like build and run and configure and kind of learn how to do all the stuff on your own. And some people do. Like I think, you know, I'm not really sure, but if you're not really supposed to cite people who aren't your customers when you're a vendor, but like the Chick-fil-A people in the States, they're a fried chicken restaurant. They gave a recent overview of how they do Kubernetes stuff. They might like license it from someone. But, you know, in reading through what they do and if you look at like what our customers do, like they got other stuff to do.

Take care of Kubernetes. I'm no longer astonished, but over the past five years, you know, I have another podcast that I do, Software Defined Talk, and we cover Kubernetes here to here, week to week. And there's an ongoing joke that like, you know, not each week, but we would often discover that there was something that Kubernetes didn't do that I assumed it did, right? Because if you kind of read about how great Kubernetes is, it seems to basically be like Names mentioned.

Names mentioned in English. Kubernetes is to personified responsibility to do like extensive monitoring and management, right? So we have things like Tanzu Mission Control and other things that you can use to monitor and manage it or provide all of the the catalog of services and things that developers and other people would want to use, right? So we have a catalog that does that and you know there's all and then you know the way that you enforce security and governance and then one thing that's like hard to capture is like

Let's call it like the way of using it. So like, you know, the way you configure things, the way you govern it, like all these sorts of things is also not like, you know, it's something that you bring to what Kubernetes does. So once you start to think about, and again, you know, just think analogously to any platform you would use to run an application, right? Like it's a whole bunch of stuff. And so one, you need all those extra things. And then two, The other parts of Tanzu have a lot more to do with application development

If you imagine governing the long term coolness, I was going to say agility, but just like, Names mentioned in English. Right? Just you need to think how to operate it the day to all of what you said. But as well, we see that if we introduce the platform, that is fairly complicated stack, right? Because, you know, when you look at the standard customer, you have this physical layer, underlay, overlay, plus on top of that virtualization in VMs, you have Kubernetes in any form, right?

The easier it will be. And the faster you can move. One of the platforms we have is based on Cloud Foundry, as we call it now, the Tanzu Application Service. This is something that we had before Kubernetes came to dominate the container space. Lots of people still use it now to effect and they like it. That's an example of there is not much ability to customize things when you use Cloud Foundry, when you use the Tanzu application service. And what happens there is that, yes, very rapidly, people can start developing because it's all integrated there. If you imagine using a platform as a service, part of it is that you don't have a lot of choices.

Więc, co masz, to wielka skomplikacja, wielka standardizacja z, jak powiedziałeś, ekosystemem wokół tego. Więc, na przykład, jeśli patrzysz na sposób Kubernetes w robieniu stacku Tanzu, gdzie budujesz na górze, wiesz, Tanzu Kubernetes, Tanzu dla operacji Kubernetes i platformę aplikacji Tanzu, a na górze, jeśli robisz, jeśli używasz frameworku Spring, jeśli robisz aplikacje Java i piszesz aplikacje Spring Boot, There is an out of the box way to do all of that, that you can start doing things rapidly. But it's been my experience that the larger the organization, for better or worse, hopefully for better, people really want to customize and tinker with things.

But they're not doing all they can to help developers out, right? Like, which I think historically has been fine because the infrastructure people haven't been able to easily and affordably do that, right? Like, it took all of the effort of infrastructure people to just get VMs and now containers and Kubernetes clusters to developers. But, you know, I think in the past, I don't know, like, I just make up these numbers, three or so years, like more years, but Providing raw infrastructure if you don't customize it and build it on your own is pretty easy. And so what this allows infrastructure people to do, kind of as you were alluding to a little bit, is to think about how can we solve more of the problems of our customers, the developers, right?

I to, co te organizacje znalazły, i to, co zostało wyrządzone w wersji Kubernetes, w stacjach rozwoju aplikacji i rozwoju stacjów, w dodatku do tzw. Tanzu, jest to, że generalnie polecam, że od samego początku jest to dobry pomysł, aby poddawać się w pełnym czasie jednej osobie do tego rola rozwoju aplikacji. I chcesz, żeby ten rolę nie była tylko The solution engineer, DevOps engineer, people who are kind of like going over not only the training of it, but also kind of like crafting those tools. But this, let's just call them the internal DevRel person. The DevRel's job is exactly, is only what you were pointing out, is to just raise awareness and interest.