Laksh Manan

Yeah. I'm Lakshman. I have 2 3 plus, uh, years of experience in Nuance Tech. I'm currently working in Hariburu Technology Private Limited, and I'm working as a back end developer here. Before I worked in functions of IT innovation, there I completed 5 projects. Here, I'm working on 1, um, medical related project. Uh, Yeah. That's about me.

I will use any external tools like user profiling tools, uh, that is node timing, uh, and 0 x to performance boot bottlenecks. And after that, I will use APM, that is application performance monitoring tool, uh, like, uh, New Relic or Datadog, any other. PM 2 also, it's a good fit for this. And after that, uh, I will log that activities, users' activities. After that, analyze with that, uh, active, uh, that active logs or some other details from the users. After that, I will optimize the code. If any, um, additional loops or something there, that means I will try to optimize that code. After that, uh, database queries, I will check if if we can able to reduce that. Uh, I will try to use any aggregation easy pipelines, uh, if they are using any complexity in that. After that, I will implement load testing. That is, uh, how much data is coming, how we are loading the data.

Yeah. I will use that middle bus to implement layers to one database to another database using aggregation or catching method. After that, join data both the places, like, uh, merge them in a single application logic. After that, data consistency. Uh, I will use identifiers across both, uh, databases to reference related access. After that, I will create the APIs from both side, uh, from MongoDB also, SQL also, and I will increment, and I will get data from both the places. After that, I will cache the data, and I will reuse.

First, I will choose any, uh, catch store mechanism. Uh, I will choose Redis. Or if you want to go with any other things, note catch is there. After that, I will add that catchy layer in my application. And then that I will set some expiration for that. If, uh, any data is additionally adding this, that time it will expire and it will refresh again. After that, a catchy key design, I will do for different queries to avoid and data overlap. If we are doing 2 or more queries, that time, any overlap is happening. That one, for avoid that one, I will add catchy key design.

I will use any use state management Redux or MobX. After that, component level state, I will maintain if we are using any use state or and use reduce it for local state within component. Either I'll use after that context API, I will use for sharing the, uh, state across components trees without props doing. After that code splitting, I will split the code, and I will maintain the code quality. After that, uh, persistent state paths, and I will use to process the data.

First, I will select the 2.2 plan taxes based on our application means. We are going to authorization code flow or any other bearer token kind of thing. After that, register I will register the client using client ID and client secret. After that, I will implement the redirect URL to that which you, uh, URL we are going to redirect the user. I will mention that. After that, I will request the authorizations. After that, every endpoint inside authorization, I will send. I use authorization. I will request access token from work provider. That request token, I will access token, I will send to in every endpoint. After that, I will securely store that access point in HTTP storage or some other secure place.

Yeah. 1st, I will validate the email using rejects. After that, I will check that user ID is there or not from params. If it is a valid, uh, ID or not, I will check using mongoose or mongodb. Any package validate. After that, I will check. After that, uh, that user is they are not there checking. Before that, we can, um, use that as in function. I will improve that error messages. Uh, it's contained the status only. That message we are sending, I will give that error, particular error to the user. After that, I will add that try catch inside, um, from starting to end end of the program.

If the infection is happening in component mode case, uh, it's correct, but it's in in modern React. Consider using useEffect instead of this. We will use that useEffect to render whenever we want. We are giving second parameter, same t, uh, array. It will render on time. If we are if you want any particular values updating time, we need to render means we can use that, uh, array inside parameter call. Now we are using items. That items in the update is happening means in array, packet inside, we can view that item parameter. When and, uh, when that item is changing, automatically, user will run.

What's up? For server side rendering, uh, React providing an exchange of, uh, an exchange framework to utilize the server side rendering and the SEO friendly kind of things. They are already implemented in their framework inside. We can install that framework. Inside, we can, uh, use Node. Js to run back end services. In Node. Js, we can use Express. Js. It's fast and secure one. After that, we need to install the packages necessary packages like React and React DOM and React DOM server to install that expression. I will use that, uh, client side, uh, hydration to ensure that HTML, uh, pages or client side is working.