Sanjay kumar jawahar

I have around, uh, 7 years of working experience, uh, as a push to a developer. Uh, but then, uh, multiple domains ranging from CRM, ecommerce, and, uh, in, um, uh, electric vehicle charging mobility solutions. And, uh, on the technology front, uh, worked in Java, JavaScript, And in the front end, uh, as well, you have a experience with the libraries like, uh, React and Vanilla JS as well. And in the back end, uh, work with, uh, Node JS, Nest JS, libraries like Nest. And on the database print, but with, uh, SQL and means relational and non relational. Uh, like, non relational work with MongoDB and time series, uh, database, uh, such.

Uh, I'm not, uh, having a word with the Angular, so I would like to skip this question.

Actually, 2 uppercase is, uh, it's called as an object, uh, little here. Uh, but what we can it is a method. So we have to just close it with, uh, the braces. This is this message.

Why? Why? Why? I think, uh, I don't find any issue in this call. It should definitely work.

So, basically, we can just use some, uh, response, uh, monitors. Like, uh, I don't get an I don't remember that those names. So we can just do, uh, do the testing, uh, like, the stress testing. So multiple times, we can just call the API and, uh, check, uh, whether the performance is good, and each time the data is widely, uh, sent to the client. So those things could be done. The profiler could be used, I guess, similar to the form of React JS. That is something, uh, I don't get the name. I used it, uh, earlier. That's doable. That's that's not be a problem, I guess, from my end.

So as loading itself, uh, is a multi core multi core app, so what we can do is, like, we can just, uh, replicate replicate the application, uh, in that exact instance and, uh, could be made accessible and be more available to the client. So I haven't used the AWS Elastic Beanstack earlier, so I'm not uh, sure on the exact application on what it does. So the thing with Node. Js is we can obviously just work on the core. We can just split the core and, uh, make the core available for each instance of the application. And, uh, we can just split the CPU's performance to each core, and that could be, uh, achievable, but not sure on the elastic being stacked in. Thank you.