Santhosh D S

Okay. So sorry for the delay. Like, uh, yeah. So myself, Santosh, and, uh, I've been working as, uh, like, a team leader at the Ideakrishta Solutions Private Limited. And I have a a very good background, uh, in different programming languages starting from JavaScript, React, React Native, Angular, Ioni, and, uh, all the experiences in-depth, I would say, like, rather than at the very top level. And I've already I I do also know Android native development as well and, uh, hybrid app development using Ionic and React natives. And, uh, I have exposure towards augmented reality and virtual reality apps along with IoT devices as well. In the past, right, I have worked with the ESP 8266 and coded some program, coded some, uh, what to say, actions and tried to do various different IoT products. This is using SPA 2 double 6. And I've done some certification in AWS IoT Core as well. But it's been almost two and half years, uh, that I did IoT AWS IoT Core. Uh, but if you look at me, I've been, uh, leading a team of, uh, 5 to 7 members, and I'm, uh, very, uh, proficient at what I'm doing. And, also, right, like, uh, I I have a full AWS exposure on various services. I do know about CACD, DevOps, uh, full end to end. And, also, like, uh, I do use CloudFormation, uh, uh, to maintain my code as, uh, my code, uh, deployment code. And, uh, like, when it comes to my work expertise, right, I've almost 7.5 months of work experience and 2 years in Android development and remaining 5 years on the web development, both the back end and front end including. And when it comes to database, right, RDBMS, I've worked with MySQL, Postgres, Oracle and SQL and when it comes to NoSQL databases, right, like, I have work exposure using MongoDB and DynamoDB as well, but it's kind of moreover like MongoDB I've pretty much used. And, uh, uh, expertise wise, right, I'm capable of doing most complex queries in both MongoDB and RDBMS. Okay? Uh, and also, right, uh, like, uh, when it comes to particularly IoT, uh, like, I don't have really much experience, but definitely damn sure I can say that, uh, I have the explorative skills to quickly learn and, uh, get it adapted and become an expert at it as in very short period of time, I would say. And I have done the projects using that course, right, which are related to things, devices, all those things. Right? Like, I I I did pretty much, uh, got a good score at IOT core. Yeah. That's all about me, I can say. And, uh, I I I've ran my own product as well, which, uh, from scratch, I've developed and, uh, like, uh, maintained it, uh, for 2 years. Okay? Uh, with all CICD, uh, DevOps, so that that is required maintenance and, uh, like, a lot more I did, I would say. And what else I can think of? Yeah. I work with

How do you keep up with the latest coding developments and programs? Yeah. So I do keep attending webinars and, uh, like, uh, the latest blogs from the respective programs. Right? Say, for example, when it comes to AWS, I do keep attending the AWS reinvent to keep myself updated with AWS stack. Vice versa, uh, like, uh, for anything related to AI, right, AI stuff, whichever is new to the market. Right? I do keep trying that. I do try on my personal laptop where how it works and how it benefits us and try to analyse more uh on that and see if I can think through, if I can contribute to them or how I can make use of it. So I always think from my own perspective of how that can be beneficial to me and the society uh-uh in in which I can play some role within that. Okay. So, say for like uh, that my recent, uh, uh, learnings is OpenTelemetry. So there I did explore, uh, ADOT, AWS, uh, Distro for OpenTelemetry, and, uh, I had contributed for minor corrections within that. And also, right, I was able to customize a few libraries for ourselves and use it for our team, uh, internally. So it tells like, I do keep myself up to date with whatever releases are being done and keep trying it and also right. Uh, I do figure out myself, uh, like, joining the webinars or, uh, like, any attractive uh-uh, attractive any classes like, say for example, right, I I've been, like, subscribed to solid principles, keep attending and trying to make out of it how differently they explain the concepts and vice versa. Like, stay in the market reading the blogs, right? I do uh that log what I've learned and keep practicing it across whatever modules I do work and think innovatively, uh, how it can improve ourself. So, like, uh, I do, uh, follow these steps particularly, and I do also join courses in Udemy to, uh, stay on top of, uh, uh, what other people have gained from that. So it's it's kind of like, uh, I do keep looking at things in the internet itself to figure out how I can improve or what I can learn out of it. If something I can teach, I do write blogs to help others learn from it. So this is all about myself staying in touch with coding developments and programs and a bit of practicing algorithms uh, whenever it is possible. But it's much over, uh, in a stretch I do pick, but otherwise, right, uh, not on day to day basis. Say, some 20 days I do on a stretch, I do pick it up and practice it, but not on, uh, really, like, a day to day basis throughout the year. Yeah.

Uh, my my favorite programming language is about, uh, I would say Node. Js so far, uh, because I'm, uh, like, JavaScript only, like, technically. So because, uh, initially, I started with the Java. I was very impressed how it works really. And, I used to work on Java, and I had a lot of interest in learning Java because of hoops, I would say. Because the way the, uh, I used to I got trained with, uh, like, cue spiders, uh, in my early days. And it was so inspiring. Right? Like, when he teaches hoops, right, uh, with interfaces, uh, I I got a bit of addicted to that, like, how it works like that just like that. So it's a bit of, uh, like, early trends, I would say. And later on I stick to JavaScript, shall I do, uh, know Java very well and I do keep looking at it. But I I as I worked professional, right, I've got more approach to into JavaScript and I've been working on JavaScript, uh, like, uh, pretty much almost 5 years. Started my development with React JS first. And it was very trend, uh, trending at the time when I was joined React JS. Uh, so, like, it's kind of from there. Right? I used to, uh, just, uh, see behind the scenes how they did React, uh, what is that React internal concepts, how it works. And pretty much did Node. Js as also. And, uh, I I feel like I'm more comfortable with Node. Js. Js. Uh, I wouldn't say I'm not good at, uh, Java, but, uh, it's kind of like I've been as a work professional. Right? I've been practicing JavaScript for almost, uh, as I mentioned, right, 3 to 4 years plus. And, uh, like, uh, I like the simplicity of JavaScript. Uh, similar to Python, I would say, but, uh, like, moreover, right, it has, uh, now added a bit of TypeScripts. Right? It feels more of a like a Java itself, and you can apply most of the roots concepts. And, uh, pretty much, uh, write good code, uh, which involves a solid response and also, right, like, uh, implement some design systems, uh, DDD, whatever it is. So I like the way we write the the code. Right? And, uh, we think of the business and convert that into code and play around with it. So it's all, like, uh, out of my interest. Right? Uh, Yeah. JavaScript type, I feel very much, uh, my favorite language as of. And, um, yes. Yeah. That's what I would say. That's all. Yeah.

When application you build and which technologies you use to build it. Yeah. Yeah. Uh, I would explain about 2 experience each 1 minute. So one is, uh, for a client called, uh, I wouldn't want to mention the name, but, uh, for a recent client, right, I did work on supply chain, creating supply chain, where we have to work with, uh, how does a material get produced and what is the emission that it gives from scratch to till it's, uh, death. Okay. That is the business concept. So we did start with, uh, like, uh, we use NestJS. So like, the reason we preferred nest JS is we had a modular concept, which pretty much we need it. And also right, it allows the dependency dependent in gen c injection dependency injection. Uh, it allows the DA principles. And number 3, right, uh, we we we have an option to structurally code very well. And TypeScript, it has, uh, benefit. And a lot of predefined modules it has, which makes our job easier, which we can save time. And also, right, uh, uh, it gives lot more flexibility in adding reusable code easily. And it has well control over test unit test cases and the E to E. So, all these reasons allowed me to use NestJS and we had used Next. Js in the UI. Okay? So there again, right, like, uh, the reason why we had used this again, right, uh, it use flexible development of routing concepts that is it has. And also, it allows us to do write some server side code. But pretty much, uh, we use it as a print and application as well, we haven't used much of the back end designs. And it allows to write us server side pages. So, uh, which again, like, gives us benefit of loading it a bit quicker so that the client doesn't face uh, any issues in loading. And, uh, this is the reason we used Next. And database postgres we use, that gives you very much pretty much access to JSON as well and where we can write complex search inside JSON as well. Uh, even though if it is RDBMS. And we have stick to AWS. So that is because, like, uh, we all our existing resources on AWS and, uh, like, we have a team working with AWS. AWS. So it's always we found that, uh, that is beneficial. Okay. And when it comes to, uh, like, this is all

Explain the following cloud formation template. What is wrong with it? Mappings, region, resources, finding map. Uh, region map. Use east 1. Okay. Change 64. I don't mappings. Okay. Find mappings, region map. I'm not able to Uh, like, it shows partial partial code. It says find in map, region map, comma, after that, nothing is there. So that is wrong. Okay? And, uh, mappings, uh, we have a mapping, which is kind of, uh, uh, JSON structure where inside that, right, uh, it is all about, uh, the data and resources, right, where I it is creating an e c two instance with the properties of image ID. So, it is looking into finding map, but again, I'm seeing that, uh, I'm not pretty much sure about this syntax finding map, I haven't used it. But it tells there is something wrong because it starts an array with region map comma. And after that, right, I don't see, uh, any code written. Okay? Yeah.

An online portal and, uh, why? I think the question is not complete on an online portal. Yeah. So, usually, right, I do encrypt that, uh, and store it in the database, and I wouldn't store the plain uh, password or as it is. How would you store a user password on an online portal and why? Yeah. I don't know what is the meaning of online portal, but it is definitely great to understand what exactly is the online portal and answer to that context, I would say. But when it comes to back end, right, we do, uh, definitely, um, encrypt the password and store it so that, right, uh, no one is able to read or have access to those. Uh, and always, right, even, uh, while validating, right, we hash it, uh, technically. It's instead telling thing, we we can call it hash it. So always, uh, hashing use the same output, uh, whenever, uh, we use uh

So I do typically start my day with a scrum for, uh, 15 minutes where, uh, we do listen what we guys are gonna do, uh, for that day. And, uh, like, uh, we just, uh, quickly, right, uh, make a note, uh, out of, uh, what we're gonna do, and, uh, is there any dependencies for others? And then we get, uh, started. So when I start my day, right, I do look at the emails and what I gonna do for today, analyze that properly, and then, right, pick up, uh, items that I gonna particularly try to target. So, uh, in the storm, the same things could have been discussed and the same I itinerary. Right? I will also be relooking it after scrum and revalidating it. And any dependencies on the other people first, right, I do try to address it first and then come back to my work where I do particularly write some, uh, coding, uh, on the particular item that I do have or the designs, uh, that I have to create, uh, for the, uh, work item that is related to me and coordinate with the project manager, uh, and ensure, right, all the items are being captured and there is no any other dependency for that item to uh, move forward. And I do spend the remaining time, uh, writing code, uh, for my task. And then towards end of the day. Right? We will have a scrum where, uh, like, we'll have a scrum where whatever we have completed, right, that will be, uh, like, uh, recorded and will be updated as a status and, uh, we'll end the day. Uh, if there is anything pending, right, uh, still after scrap, we will try to complete it. If not, right, we'll keep it for tomorrow. If there is anything, uh, not urgent, we'll keep it for tomorrow. But most probably, like, uh, we do have we do plan it in such a way it gets completed. If not, I think, uh, the urgency, uh, the way we discuss with the project manager itself tells the urgency or the need for completion. So based on that, right, we try to, uh, like, uh, complete it, for that day. Yeah.

Yeah. Pretty much I used, uh, uh, cloud formation. Currently, right, with Lambda, the biggest concern is about, uh, like, maintaining the code, uh, at some repositories or s three buckets and, right, uh, getting it deployed. Okay. So even though we have, say, ACD pipelines, right, like, uh, it makes sometimes, uh, difficult. Say, for example, right, if you are binding the Lambda to, uh, CloudTrak, Okay. LambdaEdge, if you use. So it makes very difficult to, uh, manage the CloudFormation code, uh, with, uh, version codes where you have to change the key name of version code each time, and it creates a pain. Say, for example, right, testing that, uh, now even though we have many, uh, virtual boxes. Right? Uh, sometimes we it we are not able to reproduce the same, uh, like, uh, environment that we had in production or, uh, like, it's kind of which is running on the cloud. Okay. And in the local, right, uh, you do have to ensure, right, you have that smooth experience running there. Because it doesn't allow you or it creates some issues where you have to try spending some time resolving that, trying to understand why it is causing issues. On top of it, uh, you will get lot more installation issues like this. And 1 is maintaining the code, and the other one is, uh, testing testing the functionalities. Right? You do face issues. And whenever, uh, it, uh, starts misbehaving, uh, you will have very little clue what is happening. Because like millions of requests will coming into Lambda and you will be able to see the logs. But sometimes you will not be able to observe what's going on. So you need to have distributed tracing or any external things that can help you out really what had happened to analyze and figure out what really had happened. And, uh, you should have an design architecture. Right? Uh, should you really have every single function as 1 Lambda? Or, uh, how how exactly do you want to maintain? Right? Uh, that definition should be there. Or else, right, like, uh, a single lambda running for more milliseconds, uh, might not give a smooth experience for end users. So you have to break it down properly. So it's not just like blindly you write Lambda as a big function and you go it will increase your cost. So it is something right, you have to maintain the balance where you can reduce a cost being accredit and I feel like Lambda is bit costlier, but it reduces maintenance of work that you have to do. But still I would say a bit even though people sense saying that Lambda is easier. Right? Like, you no need to do any job. Right? I always have something in my mind saying that Lambda is a bit pain sometimes. Not all the time though. Uh, but if you had the right expertise, well, good, uh, but uh, but not all the people will have the same mindset, uh, that people who designed or trained the Lambda engineers. Right? So it's not the same. So I would always say it's a pain rather than gain. But, uh, shall, like, uh, it depends on application use case to use case where sometimes it is very useful, for simple use case. But when you have a complex use case with different analysis mindset, It is a pain or even

Which frameworks, technologies, and programming languages do you use? See, it's not about month or year. Right? Uh, today, we have many frameworks which use most of the features in build and where you can plug in libraries and play around. So it is all about, uh, why we have to use that programming language there particularly, say, for example, if this project related to any data aggregations, right, or any number playing side, we go with the Python, I would say. But if it is pretty much web app, right, with development. Right? I we go with JavaScript because it has more supports, uh, support towards JavaScript. And, also, right, uh, when it comes to thinking from resource perspective, right, uh, both our UI team and backend team will be on the JavaScript. So they understand what they have written. So it's almost, uh, makes easier. For instance, we'll have to look out for resource on different languages, which is sometimes it's fine, but not really in this world. Today's asked access to resources. Right? Uh, so I wouldn't think that has a problem. And but when it comes to choosing particularly, right, uh, back end technologies, we do look at whether are we doing huge processing tasks, uh, any any any like those things. Right? We go with Java, but if it is a simple REST APIs, which interacts with the database, right, without much execution, we go with JavaScript and pretty much, uh, we try to keep things simple, which has a lot more modules and flexibility. Uh, because as you have already mentioned, in a month, you have to develop. Right? We should look out for languages, which has most of the things prebuilt for that particular module, which we are designing. It doesn't say for example, if we are running some machine learning projects, right, we prefer Python and Java because most of the libraries are written in that. So it helps you to do it easily. But if you do prefer JavaScript today, right, you will be completely broken. Like, because, like, uh, it will you'll not have enough support on live queries, and you'll just be stuck, I would say, writing that code. So I would always, uh, for simplicity's sake, I would straightforward say Node. Js, Python. And, uh, when it comes to web app, uh, I would say, uh, Angular, I would uh

Within AWS, and does that include a time series? Okay. I would, I have experience in like, Amazon RDS. Okay. Uh, I would say DynamoDB, I did use, but I'm not pretty much sure about the time series, so I would skip uh

Pipeline code will code it like a script each of them. Yeah. So I haven't got much exposure towards code, commit code, pipeline code, build, and code deploy. But, uh, other than, uh, these individuals, right, uh, do does help in, uh, committing code and running some pipelines and building code and deploying code. Okay? But, uh, it is all about, uh, I heard like, uh Thank

All at once immutable. I I don't have much exposure to Elastic Beanstack, uh, deployment. So I want to reiterate the experience that I have. I do have worked with cloud formation, creating EC2, ECS Fargate, maintaining roles, policies, SQS, SNS. Okay. And then CloudFront S3, Lambdas. Okay. And, uh, SCS. So this is pretty much and load balancing, Uh, these are the things that I had, uh, exposure towards. Uh, but, uh, it would it would it it shouldn't take much time for me to get, uh, explode on this, uh, Elastic Beanstalk I'll stop deployment mode. But yeah. Yeah. Thank you.

Have you had general IoT experience? Yeah. I had a a IoT core experience as a trainee or like a learning course. So I had done some certification in IoT, internet of things but I think it's been 3 years back and I've learnt about things devices and policies, roles. These are the terminologies I do remember now, but I don't have any work work experience. And I do have worked with ESP 2 double 6, writing some code inside that and and connecting to and with that to Internet and do real time data transmit, based on whatever we do read using sensors. Right? So that is something I had really experienced that 2, 3 years back. And, uh, I've used, uh, MQTT protocols. I've used WebSockets sockets of those things. Uh, pretty much. Yeah. Even HTTPS certificate. Pretty much I did whatever we do on web development. Right? Uh, that I've tried it, uh, on that ASP 8 2 double 6. And when it comes to IoT Core, I wrote some software on it and deployed it and tested it, but, uh, it's all like, uh, in that course, they have trained But, uh, pretty much I've got a good score in that course, I would say. Yeah. Thank

Uh, issue. Yeah. I would, uh, say, uh, when I was working with microservices, right, it's really very difficult to, uh, see what happened across the board. Okay. Say, for example, right, like, uh, I started, uh, seeing some orders started failing. So we worked with one of the client where, uh, we receive millions of orders. So at particular time, uh, right, uh, we started seeing orders are being filled. So, uh, we we have no clue what where really which service is being failed. We can see the database record is marked as failure with a particular step, but we have really no clue why why that is failing. Okay. Uh, we, uh, had, uh, like, a kind of a we don't have any, instrumentation done on each service level. So it is something very, um, uh, tricky for us, right, like, uh, to figure out and we started with, uh, uh, logs, actually, and trying to figure out the sequence. Again, like, you'll receive millions of orders. We have to trace by route ID. So we used the the trace ID and, uh, started looking really what happened. Uh, we solve the problem step by step trying to analyze till this step, it has been successful and this particular step, it started to fail. So we looked at what all the external dependencies that it had and we found like it is due to one of the certificate generation was getting failed due to memory issues and, uh, we started trying to figure out why that is failing. And, uh, again, right, we don't have clue why it is failing because when we try to run it, it is just running and when we increase the memory also, it runs, decrease and when we push more load into it, it works. Okay. So it is a we at last, right, when we look looked at the, uh, libraries, uh, issues, right, uh, I think it was telling about, uh, uh, some garbage collection and randomly the issue occurs. And, uh, the solution they suggested is to clean up. Uh, but, uh, it's a bad idea according to me, like, just doing. Uh, instead, uh, just we try to, uh, pick up the garbage collection ourselves, carefully and try to limit the number of points that we store in the memory and try to, uh, improvise the efficiency in how that certificate gets generated. So that is something we try to resolve it, And that is one of, uh, the difficult time, right, where we start receiving too many orders and few of them are failing and try to rerun those. So, parallelly so we, uh, try to resolve that on step by step, and later on, we did the instrumentation for all of those applications, uh, from front end. So we made our job more easier, uh, exactly trying to figure out what caused that issues. And we were able to, uh, make, uh, uh, try to we we were able to solve more, uh, such issues after that. Yeah. Thank

Hello? S 3, uh, company data. Uh, for that, uh, resource, right, it will allow listing of bucket action run task ECS, okay, allow ECS cluster. So whenever the cluster ARN is of uh, cluster slash prod, right? Okay. It allows uh, easiest task to run on resource uh, task definition. So it's kind of like, uh, we always look at action, effect, and resource. So which resource is allowed to perform which action, whether it is allowed or not allowed. So, uh, it has it goes based on a priority and it does. So it is all about, uh, every action, right, uh, should have an, um, effect and on which resource, right, we're gonna apply that action. So that is of IIM policies. Yeah.

Else code. So pretty much right. Uh, if we found, uh, in inefficiencies, we do pull on them, uh, pull them onto the call, and we try to, uh, ask them why, uh, they have to write like that, what is the use case of it, why, suggesting them, like, uh, try to think why you shouldn't do this way, uh, and try to understand, uh, isn't it, uh, that they didn't know and they didn't write or they felt like, uh, due to time constraints, uh, they did write that. And trying to explain them the importance of writing the efficient code. So that right, they really understand why we have to write efficient code, even that few milliseconds what we say there, uh-uh, it makes a very big impact across the board to everyone, like, from the user business perspective, from the application performance perspective because, right, when someone loads some code, right, uh, if it takes more than half a milliseconds, right, like, half a second, right, think about, like, they will get a bad experience and you were consuming more resource time and, uh, more more of such will definitely make things pretty much bad. It is ripple ripple effect, I would say. So it is almost do the best by ensuring, right, you write efficient code as much as possible and reusable code as much as possible. So sometimes, uh, efficiency and reusability might not match, but, uh, take a best addition out of, uh, scenarios and the, uh, time, uh, at which you have implemented that, right, uh, in accordance to the project's importance of the project. Okay. So it's all about balancing act, I would say. So, uh, uh, to take the wise decision on doing, uh, uh, that balancing act properly.

Back end development, why did you choose to learn the full spectrum? Uh, it is not about, uh, uh, becoming specialization at one back end. Right? Uh, it's kind of like, uh, it gives me full idea. Right? How I'm writing the back end code and how that can be utilized in the front end, uh, from pagination perspective to testing end to end flow, identifying how it can behave in case of error handling. Because, uh, when you work with 2 people, right, uh, I I had, uh, take the lead to answer frankly answer to this question. Right? It is due to my interest in the overall technologies allowed me to learn full spectrum uh, because I always, uh, when I started with UI development, right, I always want to think of what I can do in the back end, why what how it works, what it takes to and how it communicates to database, right, all the things, right, it keeps going in my mind. So I just want to give it right and that way I started doing both, UI and backend. And that way, right, I was able to, uh, just do most of the things myself instead depending on others. And, uh, it allowed me to become an expertise both UI and back end, I wouldn't say like I would rather call myself expertise in both UI and back end. I had a better understanding on how understanding on how UI will work in-depth, uh, like, uh, how, uh, it makes a difference, where to put the API calls, and how efficiently I can write code in the back end. It gave me the real picture of how I can change things in the back end. Right? Typically, when I work individually as a back end developer, right, without knowing what goes in the front end. Right? I do straightforward view APIs. So but some applications it it benefits me. In some application it doesn't benefit me. So I know the real context where, uh, which makes a difference. When you want to write an independent back end code, it really makes sense uh, that back end expertise makes more sense but when you have a full stack development for only 1 UI application where you don't expose APIs or anything, right, it makes more sense of a full stack but at the same time, the full stacks can still work as a back end and uh uh

Use it for. So, uh, so whenever, uh, a queue item, right, is rejected, right, it goes to dead letter queue. So it can be used in various ways where you can rerun that or try to capture it and store it. So various things you can do. So it is all about, like, after certain retails, uh, in the queue, right, still if it fails, right, it goes to dead letter queue and it holds on for couple of days and it gets destroyed. So it is about maintaining that data. What, uh, uh, what how how, how we can use it? So practically, right, if I do say, it can be, uh, we we we had a regulator queue where we receive orders and sometimes, right, uh, even after 3 retails, right, the order still fails, right, goes to dead letter queue On very frequent basis, right, uh, we do retain those and, uh, try to run, uh, push the DLQ into the manual queues and try to see what is causing that failure. Okay? And, uh, then kind of, uh, try to run 1 certain order in our mission, uh, against a local environment by producing that if not possible. Right? Uh, we do, uh, disable all the, uh, right assets and try to read and alone and emulate that behavior so that we really understand what is happening and work against that. So it helps you to figure out what is causing uh

So EKS, uh, Kubernetes services by AWS. ECS, uh, again, like, container services by AWS and Fargate is again one of the auto managed container services where it manages us, uh, the containers, where in case of ECS, we do manage for ourselves. And EKS, I'd say Kubernetes cluster, I would say. So, yeah, all 3 had its own advantage and disadvantages. And it's kind of a case pretty much, uh, you can use standard Kubernetes practices that can be applied where AWS manages Kubernetes for us. And you can pretty much write all the codes that you want on it. And easiest, uh, again, it will it is almost similar to Fargate, but a bit differences where Fargate is fully managed by AWS and ECS is, uh, like, a managed service where we have to manage things ourselves using the concept that, uh, AWS has

The team to that group. After the team finishes setting your infrastructure up, leave your project, what actions you should, uh, take. Uh, so remove all the permissions and delete the time user so that, right, all the required, um, see, there are 2 different things. One is, uh, DevOps, uh, group permissions that have been used across our infrastructure. And the number 2 is the user IAM roles, uh, which has been created for that particular freelancers. So we do remove the roles, uh, users created for those freelancers. We delete those. Uh, remove assets against that. Remove all the group assignments added to those. So, uh, that really use control over because we shouldn't remove the permissions which have been given to the infra based on the tools. So we only remove the keys or we can say the users that has been created on behalf of those users, freelancers. So it reviews but pretty much good control over, uh, 2 different things. And, uh, yeah. So, yeah, remove those DevOps group, uh, from that other group pretty much, uh, I would say. Yeah.

User demo, uh, demand. How would you integrate AWS Elastic Beanstalk for deployment? I don't have experience with the AWS Elastic, uh, Beanstalk, but I, uh, definitely, I I do know, like, uh, you can add a load server and, uh, scale things, but I'm not I don't want to just tell you wrong answers. I'll just pretty go back to, uh, on exploring, uh, this, how I can work, uh, like, uh, think of and come back and answer this. Yeah. Thank you.

10 node applications. Uh, pretty much, uh, by, definitions of redirecting all the endpoints to UI on any endpoints with slash API redirect to the node application, uh, the respective node application. Okay? So that is how routing will be done. Versioning again. Right? Versioning again. Right? Uh, I would pretty much go with release version numbers based on dates. Okay? Uh, but, again, right, it depends. It depends on various factors, I would say. As of now, uh, I would think of, uh, based on the release version, uh, we do version, uh, AP gateway as well. Yeah. It keeps both UI and back end