 Good afternoon, everyone. I know the next tone is they're going for a lunch, but I'll make more interesting. Don't worry about it. I'm Bhuminathan. And thank you for the quick introduction, Ron. So currently, I'm helping us as a Cisco multi-cloud architect, regional multi-cloud architect, helping Cisco solutions on hyperscalers like AWS, Azure, and GCP. So what is the experience I'm bringing here, right? I have nearly like two decades of experience. Nearly like 12 years before, I did a cloud, meaning when AWS saying auto-skilling EC2, by the time itself, I did a project. So that's one of the biggest advantage. So I did a lot of cloud migrations and cloud modernization and app modernization, these are the things. So apart from my current role, what I'm doing is I'm also doing a lot of organizing, a lot of community, and also talking a lot of the global conference. An example, yesterday, I was part of APDs delivering the talk, and also the Kubernetes user community. So I love one thing about myself, please. I'm curious to learn and share the knowledge. That's about me. And apart from the technology, I also do mentoring. If you guys need any mentoring, if today I can walk, you can connect with me. And this is my LinkedIn. At any time, you can connect with me. And I have certified in multi-cloud, well, that's it. Now, let's come to the actual topic. As I told you, I want to be more interactive. How many of you guys already architected your applications in the cloud? Ozone, so, well, maybe I want to ask from Ryan. So what is the application you architected? And what are the high-level key pillars, maybe you considered. Ozone, that's great. So what are the key parameters, kind of like a key pillar, you consider when you do the architecture? Traffic, perfect. Okay, because it's kind of like a machine learning, compute intensive, so you need to be like a network, how the network can be there. Those port is like high bandwidth available or not. Maybe I'll take one more question. What kind of application you architected? Is it like a data center migration or like any specific application contact point? So any key things you consider, like we're doing the architecture? What was there like a push? What I'm asking is, what is the business push and what is the technical push doing the architecture? Visibility of the infrastructure? Reproduce, okay, got it, immutable. Okay, awesome, okay, okay, awesome. So I'll just like summarize, right? What Ryan says is Ryan focused more on performance efficiency. That's his key thing while doing the architecture. Whereas, may know your name, sorry. Herdy, okay, Herdy says more on operational excellence. How it can be like remutable, kind of like, I can do that. So for a sake of understanding, I'll take only AWS, how you can do the AWS architecture in any, that's common for Azure or GCP or Oracle or anything. But for the easy understanding, let's take the AWS. So there are like five key things we need to make sure while doing any architecture. First thing is, as Ryan mentioned, performance efficiency. How our workload is going to deploy in the cloud and going to operate in the cloud? Because at the end of the day, they are architecting for the applications. Applications is nothing but the business outcome, right? So the business needs to run, it has to be performed efficiently. So that's where like you have to use, you have to select the proper compute, proper network, proper storage. If you remember the rain word, he told it's a compute intensive application and network intensive procurement, like high GBA, those kind of stuff. But if you see Herdy, he told it needs to be elastic. That's where operational excellence comes with the picture. So most of you guys come from like DevOps or platform engineer or SRE, that's where like operational excellency, okay? The third one is maybe before instead of IOS, I say, I want to hear from you. We talked about two things, operational excellency, performance efficiency. So other than this two key pillars, anyone wanted to share any of the key pillars which you did architected, such and you wanted to share here, okay? Okay, got it. So such in concept is cost optimization. See, so we are always doing the architect for the business push. So business is always like what's the cost benefit? What's the cost optimization? I can do that, right? So this is like a third pillar, cost optimization. How do we do the cost optimization? So that's where we have to use the latest one example where our infrastructure is running more on the compute instance. So we need to use the latest one. We have to use more kind of like a later technologies like a cloud native kind of containers or serverless, those kind of stuff. So you guys only said three key pillars, performance efficiency, operational excellency, cost optimization. Any, I told you like a five key pillars in architecting anything and I wanted to be more interactive. There are two things remaining. Anyone wants to touch base? Just think from your own experience. What does it matter for your organization? What does it matter for your customer while architecting any application? Exactly, that's a fourth thing. Security, because why we have to consider if we are architecting in the application, if the application or is not secured end to end, how our customer can deploy that, okay? Or like how we can deploy our BFSA or like a banking applications on the cloud. So security is the key pillar, okay? This is the fourth one. The last one is, okay, the last one is, okay, before I complete the last, okay, the last one is reliability, okay? What is reliability? See, I'm talking now. We are connecting all the ways, like in person, also online, reliable, right? Like if I'm, if anything, if you guys miss it here, some of the people can share from the online also and it's available at the recording also. Reliability comes from the resiliency, okay? It has to be available all the time and if you remember the famous quote from AWS CTO, where it works, everything fails all the time, okay? So the reliability, so let me summarize what are the five things, okay? Reliability, performance efficiency, operational excellency, cost optimization and security. You guys got it, right? Now let's come back to the architecture, okay? So this is like a sample of, there are like, I'm going to introduce five patterns, but let's quickly take the pattern number one. Pattern number one focuses on, let's take like a normal from web application. When you are designing the web application, if you think whatever the five key pillars I told, it will be here. So we are choosing the compute and also we are here in the one of the availability zone. So what is availability zone in AWS is, it's more kind of group of data center in a specific location. So in the data, what is the data center? That's where the applications will be hosted, where the compute, network, storage, security, infrastructure, virtualized, everything will be there. So availability zone is nothing, but there could be multiple data centers, okay? And in AWS, there is a concept called region. Region is nothing, but it's a group of availability zone, maybe one, one, two, three availability zone. In one availability zone, how many data center will be there? Minimum of two to four, okay? That's these things. If you see here, we have a EC2 instance in one availability zone and we have a EC2 instance and another availability zone also. On top of that, so that's where like our application is residing. On top of that, we have a load balancer, okay? What did it say, this architecture? We are deploying the application, compute intensive application. If anything happens on AZ1, so when I say AZ1, it's availability zone one. So we have a traffic distributed to AZ2 also. It could be like an active passive or like a load sharing. Both of them is available. Let's see the pattern two. So if you guys see in the pattern one, it's more kind of single instance, okay? One EC2 instance in availability zone and another EC2 instance in availability zone. It's more kind of like monolithic applications. How many of you guys already working on microservices architecture? That's a de facto standard, right? It's becoming, so let's consider those kinds of microservices, okay, compute like cloud native. If you see here, we have like a group of instance. What is the benefit of cloud native instance, right? I've hardly correctly mentioned elasticity. We can easily reproduce and within the nanoseconds, we can easily build it, okay? So with that, we have a group of instance in one availability zone. If it gets files, we can take it another things. So it keeps on doing that. So the third one is that the region comes into the picture. If you see the user is there, they have like a web application in one region and mobile application kind of like mobile app in another region. So what does that mean? If you take like a three-tier architecture, web can be, we can use in one region, app can be, we can use in the another region also. It based on the design. But what is the key outcome here, right? You can distribute the traffic accordingly. Most of the times like a global traffic, that's why like AWS has the CDN and route 53, we can have the global network traffic. From there, we can route over this kind of traffic to this big layer. Consider an example. If you're accessing amazon.com.g, those kind of track picks loaded, located to like Singapore data center. If you're opening amazon.com.in, it goes to India data center. That's those kind of designs, okay? And those entire database also, that's what I wanted to try. The customer data is also located based on the region. This is more based on the application requirement, okay? This is the fourth and final. I know like I'm going little fast because of running of time. But what I wanted to make sure is the five key pillars you need to remember, operational excellency, performance efficiency, cost optimization, security and reliability. And you know how it is. And whatever we are talking, it's more focused on reliability and scalability, okay? So let's take our last one. This is like, I explained about region, right? By seeing that, what is the one thing comes to your mind related to application? Do you see like this application is active, active? Anytime. SLA, Ryan mentioned, right? Here, be able to achieve the SLG. Because it's kind of like active, active. They have like a group of applications in code, consider like a code banking and I will do zone A. Same thing available for zone two also. And across the region also. What is the region? So Singapore is considered as one of the region. Under one of the region, we have like multiple availability zone. Under one availability zone, we have multiple data centers. Same Singapore, we can have a Sydney. Sydney is another region. And we can have one more region in India, Bangalore, or Hyderabad. That's another region. Or like US, okay? That's how we can scale the architecture. So within the stop time, I wanted to take couple more minutes to answer the, to take out the questions. Yeah, thanks a lot. We have about three minutes for questions. So maybe two questions. And I'll be there. If you have more questions, I'll be roaming here. I'm happy to explain you. So now you guys, yeah, please, please go ahead. Okay, whatever I talk to is more focused on scalability. But as part of the reliability, right? But not reliability. In securities, I release everything. One example depends in depth. Whatever I'm doing, like one example here, it's more focused on the compute trade. You need to, what are the data resets in the compute? Have to be encrypted. Data in transit. So data in risk, data in transit has to be encrypted. Along with that, we need to include the zero test model also, who is accessing, what is the authorization, and what is the authentication, everything. So that's a key thing. Also, we need to do defense and depth towards the cloud, inside the cloud, and outside of the cloud, okay? So this is more focused on reliability pillar. Any questions? Thank you for asking, I appreciate it. So you guys got it, like, how do we scale step by step? You see, like, from one availability zone, one data center, one instance, and then compute instance, and cloud native, and multiple region. So that's how, like, we scale the things. And I think I'm running out of time. Next is lunch, right? Okay, we have one more speaker. Okay, perfect. So I'll be there. If you have any questions related to that, you can ask me. In the meantime, this is my LinkedIn. You can connect, and we can explore, we can exchange your things. If you have any questions. One more minute, right? Oh, okay. Maybe I can wait for one more minute until the speaker comes. I'd love to hear any questions, please. Okay. Resiliency. You already answered the question. Yeah, yeah. That's a very good question. Maybe let me summarize. So what is the need for multi-cloud in terms of resiliency? Because resiliency can be achieved with the single cloud provider with the help of multiple regions. That's correct, right? Okay. Multi-cloud push not only come from the application, it always come from the organization. Why? Because there are two business benefits. One business benefit is consider, I'm a customer, you are a, you are a cloud A, and you are a cloud B. I can negotiate both of them, trade off. Okay. And some of times my developers will be there. He's killed on cloud A, and he's killed on cloud B. So I have the providing the democracy. To flexibility to the developers. These are the two things apart from resiliency. Okay. Perfect. Sorry. When it comes to business, that's the first one, but it's strategically, that's very important, right? Because some of the times, you know what? You take like one of the government organizations in Malaysia, they may have, I want to store my data in specific cloud, where the data centers already in Malaysia. If you take cloud A, B, they are not there. Cloud D is there. If you take like Indonesia, Google is there. Google data centers there. So it depends on business, complaints, and also business application requirements. These are the three things. Along with that, in single way we are saying calling a resiliency by adding a spot of the architecture. I hope like I answered all the questions. Please feel free to reach out to me anytime.