 All right. Hi, everyone. How are you all almost there? Almost there. All right. I'm very excited to be a speaker for this conference. I remember last year, the first one, virtual Aya from my team did the presentation, and it was one of the best sessions rated there. Very good job. And then we wanted to better than that this time, right? So guess what? I think there are a lot of, I learned a lot just in the last two days, talking to a lot of you guys. Really, really, I want to congratulate each and every one of you. This is a very, very, very big milestone. Congratulations, guys. All right. I am Srinivas Peri. I'm a director of Ethos Cloud Platform, and today I'm going to share here the story of what we learned. All right. This slides are moving, I guess. All right. Yeah. So before we go deep into the technology, I think let me just hide the high level. We have thousands of services. Adobe has thousands of services, right? Where are all these services? So there are three clouds, document cloud, creative cloud, and experience cloud, which are powered by lots of products and services. And which in turn depends on lots of platforms, machine learning platform, content platform, data platform. All these services are built on top of Ethos, which you see at the bottom, which is built on top of AWS, Azure, and we also have a data center. So let's pause here for a second, right? I think when we say a developer experience, what exactly do we mean by developer experience, right? Let's take some personas. So you are a developer, and you just started in a new company or started a new project, and you have to get going, right? So you probably are thinking about which language I should use, and how do I get started, what libraries I should use, what are the secure frameworks, and everything that relate to about the local development. So what are we doing right now to solve the pain for the developer, right? At Adobe, we have some of the tools to generate the initial thing, and we also have developed ASR. We gave a talk a little bit earlier today, which is Adobe Service Runtime for the Java libraries. The glass is half full and half empty, but we have some story going on here, right? So the second one, Integrate and Deploy, that is what this is all about, and that's where we are using Argo a lot, and we will talk about it. And last one, Operate and Improve. Again, I would say we have a lot of tools and lots happening, but still, again, glass is half full and half empty, and I'm looking forward to learning a lot, what Intuit has built around MLOps, all right? So let's talk about a little bit of a journey that we have gone through in the last few years. There is also a lot of journey even before 2015, which I'm not going to talk about, because there is not enough space there. So 2015, if you think about what happened in 2015, right? If you have followed, Adobe is one of the successful companies who have already implemented the subscription, and Wall Street has already started rewarding us. We are already there. We are a cloud company. Everything is working, right? So what is there? So then it was all done by 500 plus AWS accounts, 10,000 plus Jenkins machines, it's all working, right? Okay, so let's do something about it. So we said, okay, containers are also coming along. Okay, let's start a platform, right? We started a platform. Look around and saw two options, right? VCOs and Kubernetes. VCOs is used by a lot of big companies, Apple and everybody else, and Kubernetes in these stages. So we made a decision. Yeah, okay, let's go with VCOs, but one of the smart decisions we made during that time is let's build an abstraction. We did build an abstraction for developer experience in 2016. Big deal, right? I will tell you a little bit about how it has helped us. So we built an abstraction for developer experience, and we got all the DCOS clusters. Platform is all building, right? So that's great. So what are the big lessons that I want to learn from here is build an abstraction when you have to, okay? Let's move on. Building a platform is one thing, and getting it adopted by everybody else is at another thing, right? So what did we do? We have done something, what we called as a platform champion, right? So pretty much in every product team, we went there, we sat, we went to that location, we made a road trip, we went there, sat down for a week, and then we told them that we are coming, and then block your sprint, come down, come here with your laptop, and they leave the week with one of the service working, right? So that's how we were in a single calendar year, we were able to get the number of services from two digit to four digit, 1,000 plus services in a single calendar year in a DCOS. Oh, cool, awesome, awesome, awesome, awesome, great story. We were all clapping exactly like this. Then what happened is Kubernetes matured. Guys, Kubernetes has matured. So it's time, it's time to, oh, Kubernetes, what about this Kubernetes we should do? Then our abstraction came in very, very handy. We have used, we have built a lot of migration tools, and again we call it as a migration as a product, and we were able to, while everybody was deploying, while it is flying, we shifted the DCOS clusters into the Kubernetes clusters, thousands of services, right? Big, big, big achievement for all of us, okay, which is great, okay? Clap again, clap again please. Exactly, that's what we were clapping also. Then what happened is, so with Kubernetes, we were also, we could do something that we did not do with DCOS, right? With Kubernetes, we gave two offerings. Internally, we call them as a CAS and PASS, and Rohan also published a blog around this. So essentially think of CAS as a paved path, and PASS, go wild, DIY, give you an in-space, do whatever you want. And we could not keep up with the pace of the Kubernetes innovation, and all the stuff that we did for the abstraction behind it, it's all homegrown tools, right? So we had two offerings, we said, go use the DIY PASS path, right? Guess what? While this all is happening, the number of services on the paved path was 3000 plus to celebrate, but the number of percentage of the namespaces that are on the PASS are like 80% of them. Essentially the problem when we started, when we have lots of Jenkins, everybody's doing DIY, guess what? There's spinnakers out there, there's everything out there, and then we have that. So that's when Argo came to rescue. Hey, why? Why? I mean, we looked at it. GitOps is coming up, cool, awesome. What is the best GitOps tool out there, right? And then definitely we want to this time learn from what we have learned in the past, and then Kubernetes, and then Kubernetes native, and all that stuff. So we put together a hackathon, we put together some teams, and then we were able to build a solution. I'm happy to tell you all that we are going GA in three weeks. That's fair. Before you guys clap, there are two important points I want to kind of mention. Whenever you do a project like this, it's not a fancy technology, you're going in a room, and then you come together, hey, product, do you want to take it? It doesn't work that way. You need to work with your lighthouses. I want to call out if the lighthouse teams are here, my two lighthouse teams, which are sitting right there, their support, without their support, it does not happen. Right from the get go, they are telling us, this is what we need, this is what we need, just build it enough so that does it have a, is it really worth it? Do we have to do it? They help a lot in helping the shaping the flexible CICD that we are talking about. Without that, we could not happen it. Let's give you a big round of applause to our lighthouse teams. Second thing I want to call out is think about the engineering team that is going through this transition. They build a lot of software and after some time, they are moving on to the next one, right? It takes a lot of guts and energies to be able to don't attach it to the stuff that you are doing it, as you're moving along, do it enough and then move on, right? I want all the Adobe Argonauts to get up. Let's give them a big, please stand up. Please stand up, all of you. Let's give them a big round of applause, and there are many other colleagues. All right. Is it feeling good so far? Okay. All right. Let's keep going. Again, I think there are a few more things that I want to, I want to go over as well. I hope this is moving on. Yeah. So I wrote a paper. Please go and take a look at it. I think each one of these books, I touched on some of them. If I really have time, oh, there's two more minutes. I can touch on one of them. So my favorite one is perfection versus progress, right? I struggle a lot in conveying. I mean, in general, these things are that part of it. I think making a good enough progress. I'm not saying don't write unit tests, don't write innovations. Please do all of that, okay? But just enough so that you are able to kind of make progress on it one, right? I think that is some of the important things that we have to learn because some of them may not stick. Some of them we have to go away, right? And for the developers who are just starting, I think it is very, very important that the way technology is all moving along. We, they have to, we have to invest on both breadth and depth, take one thing, scaling, deployment, one of them go deep, deep, deep into it, open the source code, whatever is needed. It takes 10,000 hours to be able to build that subject matrix expertise, right? You need to build one of them. And you need to also build the depth, breadth, right? Because we have to be on on call. I mean, when the 1,000 plus developers or 5,000 plus developers are asking your discussions and then we can't, I mean, we have to rotate things. We should know, we should be using our product. So I think, I think we are, we are doing decently while there, but I think it's an ongoing challenge for us, okay? We have not done it. There's a lot. There's a lot we have to kind of, as we move along, I think hopefully by next argocon when I come, I will put a check mark on the second one. And probably the third one will be green or maybe even check mark. So I think there are, there are quite a few things, there are at least four things that we don't have right now. And then we will be thinking about building it as we go along, right? We still are the infrastructure provisioning and as far as the stuff that cross-plane others are trying to address, I think we have a terraforms all over and then that is something that we need to do about it. And we don't have a unified portal. We did not bring all of them together. And the backstage is still not cutting for us. I wish there's still a journey there. So that those are the things that we need to kind of do. And what Ed talked about and what you guys talked about AI and observability, right? For sure, that is a space that we have to invest on. So I'm saying, please help us help each other. Let's make this community even better, even bigger. And we are doing for those of you who registered coming to your office today, tomorrow, please participate. We are doing some brave attempt. There are two things which are difficult in the software industry, naming and cashing, right? So tomorrow we are attempting to kind of mental model the whole internal developer experience, the boxes and then try to connect them. I'm looking forward to see you all tomorrow. Take care.