 My name is Vishnu. I am part of Tata communications. I've been with Tata for about four years now. I run the security, cloud and security, I'm part of that group. So a lot of the security engineering platforms that we are building Tata communications is part of my portfolio. I'll keep that brief so that we can get into the meat of why you guys are here. I'll get into the talk. So first thing, a little bit of a handshow. I think get a little more energy into this room. So how many of you are actually into cloud native here? Born in the cloud, cloud native. Okay, there's a few hands there. How many of you are moving into cloud native from let's say traditional cloud? Okay, I think there's a few. How many of you are here just because your friends brought you here? You have no clue why you're here, right? Okay, all right. Hope you enjoy the upcoming sessions. Fantastic panel discussion. I think I was picked up a few bits from the guys here. So thank you guys for that. So what is this cloud native push all about, right? We talk a lot about cloud native in the context of that. We're talking Kubernetes. But primarily I think there is a fundamental change in the way we work, in the way we live, right? In the way which countries are evolving, in which the way businesses are evolving, right? There's a lot of digitization happening in the world. Previously technology used to touch you somewhere, right? Some part, maybe it was the office, right? But now technology is touching you in every aspect of life, right? You've got your phones, right? You've got your mobile phones and basically that's in some sense your life these days, right? Suddenly you miss your mobile phone, you don't know what to do, right? Because the technology is in it. It's enabled you whether it's your bank, whether it's shopping, right? Whether it is lifestyle, right? Whatever it is, right? You've got everything out there and basically your life revolves around that. And technology is enabling you and the technology that is enabling it is now right now in the cloud or cloud native or as we go into the future, right? It's also going to get into the edge, right? What is the definition of edge? I don't want to go there, right? I mean, there is a lot of different edges people can talk about. But this is the way things are going, right? So let's get into this cloud native push, right? The need for cloud native push, right? So I started my career maybe a little more than 20 years ago, right? I started my career as a software programmer, right? And when I began the software programming, right, it used to be client server, right? We used to have a simple database out there, right? Maybe it was Microsoft Access, SQL, whatever, right? And then you had a layer, right? Somewhere around it, be about it, above it, right? Which you would call as a backend service, right? And then you used to have a frontend, right? Again, it could be Java, it could be C, C++, we used to do Xmotif those days. There were things around, I don't know how many of you in the room know, right? We used to do com, decom, corba, RPC, XML or RPC. So different things, right? Over the years, right? Things as they evolved, right? But the way for us to be able to take and consume the service, get data from the service, interact with the service, right? And be able to show something that is productive and value for somebody, right? So we used to do all of that, which was primarily what you call as, this thing doesn't work, monolithic architecture. No, no, no. The laser pointer. Okay, which is what you call there as a monolithic architecture, right? Simple stuff used to work for what it used to do. But the moment you started thinking about upgrades, scale, right? How do I make sure there is some kind of access control? How do I bring security? How do I continue to maintain it? Because what you build is not, its life doesn't end now, right? It's, sometimes the life is a long time. And you kind of get stuck in all of these, right? You're struggling to figure out how do I release quicker? There is things that customers are asking for us, right? But we are not able to deliver fast because you're now dependent on some other team. There's a DB team that'll tell me that, hey, I need this much amount of time. There is somebody back and team will tell, hey, I need so much more time. I've got these cycles to go through. So it starts kind of getting slower. It felt okay when we began, right? But then it starts to become slower and slower. And then the pace at which our lives are changing, right? And the way which technology is changing, right? That was no longer good enough, right? So then you kind of had this rise in the cloud, right? You had a lot of folks that said, okay, I'll deploy this somewhere. I mean, not yet public cloud, right? But somewhere out there, right? Where basically I will run the platforms for you. I'll give you the services for you, right? You can access it and then you build maybe other applications on top, right? And I don't know, we used to have something called as in somewhere in the 2005 to 2010 time frame. I think we used to call service-oriented architecture, right? You build services, right? And figure those services will give you something and then they can scale rather than get stuck in this monolithic piece, right? And somewhere I think in coding language, right? From that SOA, there was a fork, right? You got into microservices, which is what is kind of shown here. But then what happened is as we started building those clouds, right? Those clouds started becoming a little more intelligent, right? They started building, again, they started giving you security inherently, right? It started off for scale, right? Resilience, availability, all that stuff. But then it started giving you a lot of security parts. It started giving you RBAC access, right? And then in parallel, you had this explosion of open source, right? Now, when that open source explosion started happening, right? All the names that folks took here, right? Just now you heard a lot of these open source forum pieces, right? As that happened, right? You suddenly had a lot of, let's say, whether it's databases, whether it's messaging frameworks, whether it is SSO, right? You had a lot of these things come inherently into the platform, right? The cloud platform also started becoming more intelligent. And so basically what you needed is, hey, I need to be able to run applications, right? And so again, the aspect around application lifecycle management, right? How does that work? How does that scale? What type of telemetry am I looking at? What is the observability that I can get it? What is the monitoring I can get it? And more importantly, what the business is really like was that now I could get somebody to pay for something that they are using, right? Paper use, right? So that came in and so that really exploded the aspect, the business thing came in. And so now you had a paper use, right? Where I could on-demand consume services from a platform and just, let's say, build applications, right? So this, again, right? I'm not saying that maybe startups didn't exit prior to that, right? But then this really helped, let's say, startups, right? Come into a ready-made ecosystem, right? Which is where it started becoming cloud-native, right? Now, why do you want to get into startups? You're trying to solve a problem. You're seeing a pattern, a problem that is not solved today or could be solved better. But then you only have a small window, right, to get it done, right? Because somebody else could come in, right? Or in some sense, somebody could be a very fast follower as well, right? And get it done better than you, right? Once the idea hits the market. So you needed speed, right? So you started getting all this agile... Okay, cool. So you started getting all this agile development by necessity, right? You started getting all of that to get to the market quickly. I mean, this is more on the software development. But then this inherently got you the velocity to get your service or product out of the market, right? So this is where we are, right? Where basically we are spinning up in the cloud, right? In the cloud only, right? And that's basically this cloud-native part that we are. And in that cloud-native journey, obviously, right, you have all these things. Kubernetes, containers, dockers, right? I remember initially there used to be something called Rocket. I don't know where it went. But you had all this here, right? Containers, parts, the ability to spin up quickly, on-demand, on-scale, based on metrics that are getting gathered and delivering services for you at speed and to the user that really needed, right? So that's basically this whole journey of cloud-native. Cloud-native, obviously, is all right now a lot of containers. You build microservices, right? Just something that does what it is supposed to do, right? Have interfaces, right? To make sure that somebody can talk to it, right? Primarily, I would say, rest today, right? And then basically talk to each other, get stuff done, and go back to the user, right? Now, another interesting thing that happened in this, all of this, is my multi-cloud, right? So a single cloud is not enough. Initially, it was about one cloud, right? Or it's one public cloud, et cetera. But what enterprises and businesses have basically realized is the myth that the cloud will reduce costs for me got busted, right? Suddenly, you thought, oh, paper use is great. I will only pay for what I want to use. But then you end up running something out there in the cloud. You forget about it. You're screwed, right? So you basically got to a point where you are now, the cost did not go down. It looked like it would, but it didn't, right? So then you started looking, OK, how do I bring in that? Oh, no, no. I would like certain services, especially like banks, right? Or maybe due to data restrictions, right? Or due to security restrictions. There's certain things that will not go out of my data center, my private cloud, right? But there could be others that could reside in the public cloud and maybe some other cloud, right? Which could be a SaaS cloud somewhere else, right? I'm OK with the SaaS cloud. I'm OK with the public cloud. But maybe I still need a private cloud, right? So then the era of multi-clouds came in, right? Now, which is where, again, right? If you've got multi-clouds, how do you orchestrate across multi-clouds? How do I move workloads across these clouds as needed, right? How do I make sure it is secure? How do I make sure it is scaling based on the geographies sometimes, right? How do I make sure that latencies are taken care, right? So there's a lot of other things that started coming. But this is, again, purely, I would say, the cloud-native journey and basically companies embracing how to use the clouds in a very effective manner for their businesses, et cetera, to run productively, right? And the beautiful thing about cloud-native is it's constantly evolving, right? It is not stagnant, right? I mean, what technologies you have today, right, would obviously be obsolete in a while, right? But then this part around what is that next-gen technology? I mean, if it's open source or whatever it is, right? It's easily coming in, right? And there's a lot of people out there, right, in the open-source community that's developing stuff for the future, making sure you have better tools, you have better packages that can come in and address, let's say, problems that are not solvable today, or it is solved in an inefficient manner today, right? So you're kind of bringing all that. So there is just take away one thing, right? There is a genuine need, right? If you're starting something or if you're building something new, right? Cloud-native could be a very, very attractive proposition for you because you've got a lot of frameworks that are working today. Okay, next. So I covered a bit of this while I was talking, right? But then in the world that we live in today, right? There are few things, right? Which are basically business imperatives, which businesses need to succeed, thrive, right? And in the context of those business imperatives is where technology comes in, right? Technology solves a problem for somebody in a certain manner, right? So you've got to figure out what works best for you, right? Some of the panelists were saying, right, don't just go blindly pick it up, right? It may not be actually right for you, right? See whether it is actually appropriate. See whether even Kubernetes is actually appropriate for you. Look for that and then say, okay, I will adopt it, right? You get stuck with something because somebody else was telling you, again, you've got to figure out how to get out of that hole, right? So there's technologies that are available for you and some of it is basically also looking at, is it future-ready? Does the problem solve what I have today? Does it have a little bit of a life for the future, right? And can it continue to solve, let's say, certain problems for me? Because each of this, right, has a capital expenditure, there's got an operational expenditure, right? In the context of businesses that run it, right? Everything has to have, like, a total cost of ownership and be able to make sure that it can actually survive, do what it does for me today and maybe the cost recovery happens, let's say, in two or three years, right? So what are some of those business imperators? Again, these are not comprehensive enough, just captioning a few, right? But customer experiences are changing, right? People demand what they want right now in a very consumable fashion, in a very easy, simplistic fashion and in a very personalized fashion as well, right? So the experiences are really going, right, changing, right? The operational and cost efficiency is becoming very, very key for businesses, right? I mean, to survive today, you've got to be very, very efficient in the way you're working and you're going to be very, I would say, in a very controlled manner be able to take a risk, see if that risk pays off and then go large at it, right? The other thing that we talk about in today's hyper-connected world is security, right? Now, again, we are in this Kubernetes conference here today, right? But please take away that security is a foundational framework for everything that we build and do, right? The ability to make sure that who gets what they want without, let's say, with a lot of trust, right? Being able to enable those services for them is very, very important as part of the digital trust fabric, right? And I'll talk a little more. I'll talk a little more on this, right? Apart from that, you've got a lot of innovation, right? Because you stay static, you'll die, right? You say you can't change, you will not survive, right? So the ability to constantly innovate, process, product, how can I do things better, how can I bring something new to the market out there is a question on every CEO out there, right? So they're trying to really see how does this, again, technology help them do that, right? So think of these as maybe four pillars, there's probably more, but just wanted to kind of touch upon those that are major from my perspective. Now, you take these imperatives, right? And you can associate different problems around it, right? So if you take, for example, the digital trust, right? There's a lot of cyber threat attacks that are happening today, right? People would like to, I mean, ransomware, right? DDoS attacks, right? And these days, these are not even individual driven, right? These are suddenly political country agendas today, right? Trying to kind of bring down economies, right? I think this threat is real and it'll continue to be real. And whatever we do, right, in all of the platforms to inherently make it secure is going to be very, very key, right? If you look at identity access, previously, we used to have perimeters and firewalls and WAFs and all sorts of stuff, right? But then as you get into all zero trust, right? Identity becomes a key part of your perimeter, right? Your security perimeter, right? And then, obviously, we have to live with privacy issues as well, right? Data, where it gets stored, how long it gets stored, where can it go, where can it live, what is the life cycle of how long it can live, who will have access to it, who can modify it, which is my single source of truth, right? A lot of the privacy and data issues come in, right? Apart from that, when you look at process and product innovation, right, the things I already talked, legacy systems, slow to change, slow to adapt, slow to scale, right? Resilience, right? Skills available, right? Sometimes become very siloed, right? Build these technologies in which you have some verticals, right? And skills become very vertical, right? Again, you're not really able to do like horizontally stuff, right? We talk of full stack engineers, right? Full stack developers, right? Trying to cut across things and do stuff, right? And which is probably more the need of the day rather than try to kind of have siloed stuff, right? So lack of agility, legacy system, siloed interactions, so on, right? Similarly, when we get to customer experience, right? As I said, right? You need what you need immediately, right? In a customized fashion, right? If you look at all the apps that you have on your phone, right? A lot of very customized experience. But at the same time, if you're looking at, how do I get customer support, et cetera, right? People are doing contact centers in the cloud now, right? You've got chatbots in the cloud now, right? So basically, moving all of this into the cloud brings efficiencies and is also able to scale, right? Then operational and cost efficiency, right? What is my cost? As I said, right? One of the beautiful things of the cloud is it's paper use. You've got a lot of telemetry. You've got a lot of metrics that you get. You can build exactly what you need, right? Again, with the guardrails that I talked about, right? Everything, right? You've got to make sure that you're using it in the right manner for the value that you derive in the context of your use case to make sure that you're getting it within the cost structure that you define. Otherwise, it's going to bloat, right? One of the things that we used to have previously, vendor lock-in, right? You get in somebody like an Oracle or a SAP or somebody, right? Very, very hard to get them out, right? And it's designed that way, right? It's designed with that stickiness in mind, right? So it's very difficult and suddenly you are locked and you're trying to figure out, hey, how do I now change? And that itself is a big business by itself, right? So this whole migration part from one piece of software to another piece of software, right? Or even, let's say, versions of software, right? So there's a lot of aspects around vendor lock-in. But then, if you do the cloud native, go to the cloud, right? It's very easy, right? In some sense, to be able to swap out, right? And get to something new because you could have, let's say, certain services continue to run. You bring up new services that, let's say, rely on different sets of technologies and then slowly get the other one out, right? So there's inherent efficiencies, inherent advantages for you to go cloud native so that some of these, you don't even see, right? I think once you are truly cloud native, you're working in the cloud, right? Some of these problems may not even be problems to you, right? It could be a different set of problems you're grappling with, right? This I'm kind of giving you, saying that, hey, here is why cloud native is inherently advantageous for you to go, right? I think that's probably, next slide, please. Just gives you the gist of what I was trying to cover, right? And if you look at all of the cloud aspect, right? The cloud native that I just talked about, right? We're kind of getting all of these benefits inherently, right? Whether it's cost optimization, automation, right? I think fantastic with respect to being able to mimic use cases, right? Getting scale, right? Understanding if this works. Where does your system break, right? At what point will you have challenges, right? And if I am breaking here, then how do I, let's say, alternatively figure out what to do? What is my, let's say, DR plan, right? So there's a lot of things that you start getting, right? As you get into the cloud aspect, right? Similarly, right? Analytics, right? Previously, if you were struggling to figure out what's going on in which part of the system, why are things breaking down? What are my low-water marks? What are my high-water marks? Analytics is a fantastic, fantastic, and the cloud is enabled with that by design, right? You get extremely good analytics to understand what is going on out there, right? And then if you look at the whole aspect of platform, right? As I mentioned, it's now a lot more comprehensive platform for you to use, right? It's a much more comprehensive platform for you to use. And basically, you can just build on top, right? And quickly realize the value. You don't have to do a lot of things by yourself. You don't have to write a lot of code yourself, right? It's very quickly you're able to spin up on top. There's lifecycle management available as well. You're only concerned about your applications, what it has to do, how it has to do, and get the business value out, right? So Cloud Native, in one sense, jump starts, right? If you're in a business, right? It kind of jump starts what you want to do, right? And then there's a constant plethora of tools, right, that are constantly coming at you to figure out, how do I make little changes? How do I make little adjustments and reuse or use some of them, right, to figure and get better value than what I already have, right? Again, if I talk a little bit, right, in this context, right, there's a lot of, I would say, things that we do, right? I mean, for example, I've done, I'm part of security, but then there's a lot of media stuff that I've done, right? And when we were doing, let's say, some content delivery, right, that was one of the projects, products I was doing, right? We were figuring out how do I scale this to a lot of customers across the globe quickly, right? And then, basically, Cloud Native help, right, where we were able to very quickly spin up containers, right, at different pops around the globe, right, for us to cater to different customers and scale it also, right? I mean, if certain folks needed a certain stringent quality of service, right, we could provide that with a differentiated service, right, at each one of those global pops and deliver it fast, right? So the whole concept of what we needed to do, what was the problem, how do I need to address it, right, all happened, let's say, within about six months, right, which would not be possible, right, if you were thinking of this in a traditional way, right? I mean, six months itself seems long, but in the context of the problem that I just spoke about, I'm leaving out a lot of complexities, right, but it is pretty, pretty fast, right? Next slide, please. So if you look at where we are, again, specific in the context of India, right, there's a lot of government initiatives out there, digitization of our government departments, digitization of the technologies we use, right, whether it is national health scheme, whether it is e-marketplace, right, whether it's Aadha, right, there are so many government initiatives that are currently happening, right, cutting across and touching our lives, but all built in the cloud, right, built cloud with inherent security, right, with the ability to scale, right, with the ability to get you your services, right, so there's a lot of growing government initiatives and this will only grow because this is not something that can stop, right, I think beyond governments, right, I think this is something that will continue because once it's touched the lives, it's touched how we end up operating, I think there'll just be continuous evolution to that, right, business digitization is no longer some buzzword, right, it is real, right, I mean, if you cannot do this, you cannot survive, right, you've got to be able to touch every part of your business all the way from, let's say, supply chain, whether it's finance, whether it's HR, whether it's marketing, whether it's engineering, right, whether it's sales, right, it used to be a lot more metrics than sales in the past, right, but all of these functions, all of these supporting functions, right, has to be connected together in a digitized manner so that you have a very clear understanding of what is the workflow, right, and where is the bottleneck, right, where is it getting stuck, what do I do differently, right, so all of that aspect around digitization is real and it is happening, I mean, I don't think any company will survive without being able to digitize, right, so there's a lot of business digitization, I mean, I'm talking of country digitization, right, obviously there's got to be business digitizations and in all of this, right, as I mentioned, right, the startup ecosystem is booming and thriving, right, so if you read some of the numbers with respect to how many startups came in India in 2021 and 2022, right, it is staggering, right, there's about 8 billion dollars of revenue, potential revenue, right, that we are talking about in 2023 and 2024, right, it's phenomenal, right, thousands of startups have come on, right, and basically all of these are all cloud native, right, they are born in the cloud, delivering services from the cloud, delivering at speed, delivering at velocity, right, and making a differentiation for themselves, right, out there amongst their peers, right, so as this happens, right, basically the aspect of cloud native will continue, right, I think the momentum is there, there's further, I haven't touched some of these, right, but there's further increasing investments in edge and IoT and 5G, right, so all of this is again transforming, right, you're only getting faster speeds with 5G, you're getting a lot of, I would say in the manufacturing industry and maybe other industries, right, you're starting to see the value of IoT, right, IoT was a buzzword 10 years ago, I think we are starting to see the value out of that, right, and edge, right, it's not all going to be cloud native, this is also real, right, because there are use cases where the cloud is slow, right, where you've got to be able to make decisions, right, at the edge, right, for example, in the manufacturing industry, you've got to be able to quickly see an assembly line and see what's going on and you probably need an edge out there that will do intelligently something for you, right, so there are many different use cases that are coming, so the ability to coexist between the cloud and edge is also important, right, what you can do locally, you do it, be able to, let's say, shift some intelligence that can wait, right, into the cloud, right, I think that is also there, again, data is important, data is what drives everything today, right, the ability to see, inspect, make sure it is secure, right, and in the context of where it needs to live, reside, right, and in an intelligent fashion, interpret it, right, for us to then take actionable insights on it, right, so this is, again, a very key factor. Now, all of this, again, right, is kind of inherently part of the cloud native platforms that we have today, and it is all about us to actually use it in a nice fashion to then provide value to the customers. I think I'm done with that, so just a bit, if all of you can scan this QR code, I think we have a short survey that data communications is running across our customers and some of our potential customers saying how ready are you for the cloud journey, right, so if you've got this, please take a quick snapshot and if you can, please take the survey, it will be useful for us as we build our new platforms and solutions. All right, thank you. Any questions? Any questions before we close the keynote? What are the trends I'm seeing in what context? So, as I mentioned, right, customers are demanding outcomes these days, right, so previously we used to go to customers with products, right, we used to say I can solve your network problem or I could give you bandwidth, right, or it could solve your security problem, et cetera, right, I think customers are kind of gone beyond that, they're looking at solutions and outcomes, right, which is where this concept of platform is now becoming more important, right, again, you can define platform in many contexts, right, but then what we are saying is I will offer you a platform that is generic enough, let's say which will satisfy different customer segments, right, and data communications also does that, right, and then we can say, we can very quickly say, you know what, this platform then can be tweaked and customized for your specific outcome that you need, right, I think that is one that we are seeing, right. The other thing that we are seeing as people are, as we get into the 5G and the IoT and all that, right, the aspect of how quickly can you deliver that and how quickly can you deliver it at a value and at a cost that is now appropriate, right, I think so that is also very, very clear, right, so how do I bring efficiencies into what I'm doing, which is where, again, this platform concept, right, becomes relevant, that I don't have to do, I don't have to react to every customer and do something specific for that customer, right, which is where I think being able to build platforms, but again, while we build these platforms, we also get into a lot of integration stuff, right, because you've got to kind of make sure things are managed, massaged, et cetera, and you still have single telemetry, right, single views, right, so those, again, right, I would say are part of the platform builds that companies are doing to try and realize value for the customers. In a specific product, you are seeing more... I think, given the fact that this is a keynote talk, I will not get into any specific products of companies here. Good morning, Mr. Sharma. It was a beautiful presentation. Thank you for that. I have a quick question. I've been with the banking industry for quite some time, more than 15 years. You know how banking works. I've been running Mainframe for quite a long time. So what's your take on that? How do you guys approach a banking client on how to move the Mainframe system into Cloud Native? Any tips and tricks? I think it is an interesting challenge, right? We've been successful partially, right? I wouldn't say we've been successful fully there, right? But obviously with banks and then global banks at that, there's a lot of concern about data, there's a lot of concern about privacy, right? Because there's a lot of life data that is available there and how do we make sure it doesn't fall into the right or wrong hand, sorry. So there's an inherent concern about that, right? But one of the things that we are doing is we are actually building financial clubs, right? So we are basically able to kind of say that compared to, let's say, traditional workloads that would run, let's say, in public clouds or other private multi-tenanted clouds, right? We are basically telling our customers saying that how we are building a lot more security, right? And then in that aspect, right, there's a lot of compliance, there's a lot of standards, right, that we have to adhere to. We are building all of that into the platform, right? We are building all of that into the platform, right? And in a very selective manner, right? I think we are picking, let's say, very specific use cases and saying maybe this is something you can migrate, you can migrate, right? So it's a slow journey, right? But with the fintech sector coming, right? Again, those are startups born in the cloud. You've seen banks that don't even have an outlet anywhere, right? They're all in the cloud, right? So with fintechs coming up, right? I think the bigger guys are seeing that, yeah, this is no longer an option, right? This is now an SST for me to do. Again, if you're looking at customers and the scale and the speed at which they are demanding services from banks, you can't keep up, right, if you're in the traditional world, right? You've seen, right? I think you've seen, like, SDFC Bank, et cetera, given RBI, you said mandates, right, to get your act together, right? So the things that are happening purely basis the needs of customers and the fact that competition is now coming, right? So I think this is just a journey now. It started, the ball is rolling. I don't think it can be unrolled. Thank you, Vishnu. All right, thank you all. Have a great event. Hope you find a lot of learning in this event here. Thank you. Thank you. And also, thank you so much for accommodating our last-minute request and we'd like to give you a small token of appreciation. I request Sindal to come and do the honors. Thank you, Vishnu. Thanks, Sindal. And you can get the QR code from the volunteers and organizers. So if you need it, so you can request us. Maybe we have a good set of people. I think we have around ten people around, so you can reach out to us.