that. Well, I mean, technically, we did have it would be up. So it's called console, like half a quart console gave us that it gave us the service mesh with VMs, before coordinators existed, what, what what we still had heard was that we needed to manually handle the placement of VMs on the hardware. So yes, it made things easier in that, if one of my hybrid races went down, I could make assuming that I was smart enough to to use like a detached storage, like I couldn't, I couldn't move my VM to another hypervisor, bring it back up. And it would register itself and nobody would be the wiser. And all that discovery that discoverability initially was implemented with DNS, so so it, it was backwards compatible, as well. But But yeah, it was still, you were still doing VMs, you still needed to run the console agent on all your VMs. So it was a great step in the in the right direction. And like I used it for for for a long time. But what kurnaz added on top of that was the ability to no longer need the agents bundled which with each application, I didn't need to configure my coordinate agent. For my database specifically for my front end service. Specifically, I just needed to deploy my front end with the right spec, to say this is a project I need to deploy my database with, with the right spec saying like, this is my this is this, this is my database selector, and then you have a service in front of it that uses that select. So it I seek witness, some as an evolutionary change from that. I don't see it as revolutionary because I myself have has seen all the technology all over the place already. But it took it all and it packaged it up nicely, in a way that was more easily explainable than all of the individual components themselves had had it been done on VMs.