Ravi Rathod

Hello, my name is Ravi Rathod and I am working at Logistic Infotech with senior positions. My experience is 4 plus years of experience and my work in technologies are ReactJS, NodeJS, NextJS and ExpressJS.

Okay. So let's say, for example, like e-commerce applications, whenever a user added an item with a shopping cart to ensure data consistency, we can increase the quality of the item of the card and update the total price to the card. Achieving to the MongoDB with notches, we can use dollar increment method. So it will be the quantity and total price which can be identified and bypassed whenever we can use some complex transactions. So we can use some start sessions and session.start sessions. We can give to the one-by-one update and abort transactions for their handling and performance measurement.

Okay, so we can use some component profiling like component react node memo for the use memo, component wrapping and some methods we can use inside the use memo. For the slow rendering we can use some lazy loading like memory and caching issue for the identifying queries. For the MongoDB we can use some query performance optimizations like data fetching, slow querying, data management like react query with hwr, server side management, state management,

so whenever rendering on the screen so we fetch all the records and fetching gold hit once and smaller chunks and whenever the users to scroll we know it will descending to descending to the view purpose like users we can use like rendering use dot memo and memorization center state effects like based on some conditions we can identify the some of the scroll effect needs today so there's the data

So Like we can say whenever we can deal with some reading and writing data with MongoDB so we can create some start sessions and the transactions so it will help you to understand what is the execution or what will be the commit of the transactions like client.startSessions and sessions.startTransactions likewise we have some operations so it will some benefits of the transactions and when it will be the completed we will give to the bot transactions we can use some indexing like createIndex and cachingMemory for the query optimizations.

Okay, so unmounting like a glass component itself, functionality like component will unmount itself when the rendering lifecycle method is called immediately after the component is called and cleaning the background like unsupported methods, like we can use component did unmount and fetch data of the API call whenever which component did mount we can get some API request and whenever it can unmount we can cancel the request of the API, it will be useful for the unnecessary rendering and the fetch data of the component.

For the improvement, we can use inside the functions variable instead of constant or let so it will be the helpful so we can use some map method for the square inside we can sequence of array and array dot map num cross num so it will be the returning the number . . . .

So So So So So

so like we can use some serverless architecture like AWS lambda for the scaling, we can use some configurations like auto scaling, load balancing, we can fix some issues whenever we can request some specification server for the error handling, we can use some try cache and error for the mailing itself, operations for the data management, we can use some RBS and recovery replications and we can improve some AWS switch caching enables, we can add in like logging and monetization of the servers and we can add with security for the SSL and HTTPS for the authentication and authorizations

So, we can use like a route-based versioning. For example, api-v1-users.getusersdata and api-v2-users.getusersdata for the easy implementations. We can use some header-based versioning for the XAPI set v1, some navigations header for the better query optimizations, we can pass version with query parameters based on the router suggestions or approach.