Abarna Venugopal

Yes. Hi. This is this is Aparna. My name is Aparna. I'm a developer with 3 years of experience in building dynamic replication. In my recent tool at Akash tech solution as a software developer, I led development of several key projects. One of them was my model PMS, which increased the clients to over 100. I'm a I'm a fast learner who can learn quickly and adapt quickly to new technologies and challenges. I drive at fast paced environment and also have good communication. And my technical expertise includes Vrgs, Node. Js, MongoDB, Express, and Next. Js. I'm so excited about this opportunity at at app just because of the friendly environment and the strong focus on learning and development. Thank you for considering my applications.

To implement REST API in Node. Js, I'll use so we have solid and decent patterns, uh, from we have we will be having a definite structure for Node. Js. We use express. We can also use x Express to create, uh, create application that is freeform, and we create routes and controllers, and we have the common schemas. And we have we have we can use separate utility functions at all to to make it made in a loop. And the rest API, they have set of rules. Like, we can use HTTP methods like get, post, delete, and patch. Most of them, we we use standard HTTP methods which is invest we everything is a resource. So we have it has to be stateless. So every API call, we have to send all the data that is required without any having a state, uh, dependency.

We can horizontally, uh, scale our Node. Js application. We can use clusters. Um, we can we can so we can create separate Node. Js instances so we can run it. So, uh, it will be more scalable, and it increase the performance because of, uh, we have a lot of clusters, and it can be create using, uh, forking. And so we can also be use load balancing cluster from cluster of node JS application. It provides load balancing. So there are a lot of requests that is coming inside your Node JS application. So it will separate them and it will distribute the API. So your your server should be always available and performance is really high.

Okay. Mammalix, uh, they are concept that, uh, memory leaks can happen from using many global variables and closures. So we have to avoid this in order to improve our performance to optimize the ReactOS application. We have to mitigate them, uh, avoid using global variables. So avoid using closures, Like, OSHA functions, uh, which will cause memory leaks and also props filling. You don't have to send additional props or unnecessary props to a React component so we can improve the performance of the React JS.

We can use JavaScript promises. Flip, uh, JavaScript is even look it manages even look to handle the promises. Initially, we had callbacks, but promises were introduced after ES 6. We can handle a synchronous, uh, task in yeah. Just for example, I'm having an API call. So which is asynchronous. So we will get we'll get the data only after some amount of time after reaching the server. So we can handle using using the promise, uh, that is provided by ES 6, and we can then use then function and we can cut it it also has some error handling. So using promises, it is really easy than using callback center.

To configure a secured API to include data transfer notification, uh, we can use the standard HTTP methods, HTTPS, and we can add a prototype of HTTPS, and we can add SSL. So data are encrypted, uh, so it will avoid eaves dropping from any other side. So, uh, from, uh, attackers and all. So using HTTPS, uh, and properly maintenance SSL. Like, we have to keep updating if the SSL is, uh, it is expired or not. We have to keep checking on it. And we cannot we should also use, uh, several methods like stopping, uh, like, we can use validations and we can sanitize the data to to safeguard the API from attacks.

So in this snippet using a sync It will throw some error because we are throwing error in the situation. It is an asynchronous function. So asynchronous function, uh, it is like promises. It is built on it is built on a promise. There are sugar coating of that. So we are throwing some error. It will be handled using the catch.

Okay. Middleware's a function that has access to the request and response and next. We are using we are just logging that request type, like, what what method it is, like, it is a post or get. We can use middleware functions, um, for authentication purpose where, for example, you are you are using a JWT example. Here, we're just logging which type of method that is called right now so we can use it for loggers. And in expressjs, we can use middleware so we can access that request and response and next, for example, there is an, uh, default middleware express just JSON. So all the data is just passed to JSON in express. We you can access the response. We can, uh, act we can also modify the request and response and call an function. Once once the next function is called, the next middleware or the next API, which is, uh, any callback function that is set will be executed.

In reactives, we can use catching mechanism. We have catching, uh, from in the React Hooks, like, you can use use use callback sorry. Use memo with memorizes any computed result. So it is a React hook that is provided by the React so we can use it for the dependency is the same. You don't get you don't again compute the data. You don't again compute any function. You can use the same same data that is available. So if the definite is changes, it will execute the operation. Uh, you can catch catch the near cachee, and you can use it for API calls. You don't have to call again. You can check the cache if the value is already existing. And if it is existing, you can use it. Or else you can make API calls.

We can use React whose hooks, uh, to handle life cycle events. Actually, React functional component doesn't have any life cycle events in there, but, uh, they have introduced React hoops to handle, uh, state and life cycle methods and functional components. For example, you can use use effect where use effect hook to handle this. For example, we have, uh, life cycle methods of mounting, updating, and unmounting. For mounting, you can use use use effect with the function and, uh, dependency that is empty. And for updating, you can use the callback and the dependency array with the value, uh, like, uh, the dependency that that dependent have to check if it is updated. And for, uh, unmounting, we can use return statement in inside our callback of useEffect, which are which does the function of live second methods in, uh, class components.

The libraries you can use in one project can be just I worked on just, um, so we can use it in the post front end and back end. So I think it would be easy for understanding. I haven't worked on any other any other, like, Jasmine and all, but I have worked on only just so I guess I will be choosing just because it is it can be used in both front end and back end to check, uh, how the API is working and 5 I used it for unit testing or API testing. So how the page will respond for any any given input and how the API respond for any given or how any function will respond for any given input.