Laksh Manan

I'm Lakshman. I have approximately two to three 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 five projects. Here, I'm working on one medical-related project. Yeah, that's about me.

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

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

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

I will use any state management, Redux or MobX. After that, component-level state, I will maintain whether we are using any state or React's useReducer for local state within a component. Either I'll use context API, I will use it for sharing the state across component trees without using props. After that, code splitting, I will split the code, and I will maintain the code quality. After that, persistent state paths, and I will use them to process the data.

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

Yeah, 1st, I will validate the email using a package like validator. After that, I will check if the user ID is there or not from the params. If it is a valid ID or not, I will check using mongoose or MongoDB. After that, I will check. Before that, we can use that as a function. I will improve the error messages. It's currently contained only the status. That message we are sending, I will give the particular error to the user. After that, I will add a try catch inside from the start to the end of the program.

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

What's up? For server-side rendering, React provides an exchange of an exchange framework to utilize server-side rendering and SEO-friendly features. They are already implemented in their framework internally. We can install that framework. Inside, we can use Node.js to run backend services. In Node.js, we can use Express.js. It's fast and secure. After that, we need to install necessary packages like React DOM, and React DOM Server to install Express.js. I will use client-side hydration to ensure that HTML pages or client-side is working.