Harshit Bambharoliya

Good evening, I'm Harshid Bangran. As of now, I'm working as a developer, and currently, I'm working in back-end development using Node.js. So, I was previously working there and gained a level of experience with various functions. I also worked with Next.js and have experience with HTML and other technologies. So, it's my pleasure to introduce myself. I have over 3.5 years of experience, and I'm quite passionate about it. That's the introduction about myself.

What are the scheduling using effects to optimize the booking process for making your project? For optimizing React, any Webpack-like library we can use, such as Webpack. We can also use Web 3. This allows us to easily simplify the code and reduce reloading time in React and Angular, which is too low. So we need to use Webpack, and we can use multiple loaders. Like, we can compress the files, and we can

For the authentication in the AWS services, in our application, we can use AWS Cognito. Like, in Cognito, we can easily authenticate the user by the AWS service. Also, we can use multiple other services for the application. But, AWS can provide Cognito user access so we can easily log in the user and authenticate the user. Like, is it still providing 2-factor verification and all other things. We can use AWS Cognito. So, we can easily authenticate the user.

Considering high traffic for step up, how did you prevent difficult caching strategy for the front end? For the caching strategy, we can maybe use a load balancer server. Like, what we can set is we can use a DNS server, so that is the implementation for us, like, from another region, users are coming in to our server. So, what DNS can do? DNS server can do like store some cached data directly into the user's browser. Your other data will directly go from the DNS server first. And if the DNS server is not available, the other data is not available, then it directly goes to the main server. We can use a DNS service for that.

We are using one application. There is a continuous deployment process we have. So, we deploy through the CICD. So, deployment will be automatically there, so the server cannot down and a user cannot interrupt there. So, we can deploy the CICD application. So, also, I will note this down. Also, we can optimize the continuous deployment into traffic at the right time so we can easily deploy the server first.

In the React function component, we are using the state and managing state through the use state hook. In the class component, we are using state to where I already declared the state into the class component. And, whenever our state is mounted and changes, on mount, so we can use methods in the class so we can easily manage the state in the class. Like, there are three methods in the class component: component did mount and component did update and component did unmount. Component did update.

There is a Python code, but I have no idea what the Python code does. Maybe I can use the thing. First of all, my class is declared as Sales. Okay. 75. To use the class, maybe we need to call a method. Okay. I mean, there is no method defined in the class, so we can start with a hello world example.

Into the async function, we need to handle error exceptions. Like, try catch, we can put into the function. So, we need to put the try catch into the async function. That's why we can easily manage the error exceptions and handling into the function. So, the output will be there. Like, if a response should be success, then data will be fresh. But if the response is not success, then the output will interrupt. So, we can use a try catch block in this.

No idea about the robust Webpack configuration for the project. Yeah, I don't have any idea about the robust configuration for the project.

Server-side rendering is managing from the server side. So, for the benefit of the user, this is the benefit. If the user doesn't have any browser capacity to load the application, then server-side rendering will do better. Like, whenever we are using React or Angular projects, server rendering should be better. Like, whenever we are working on large-scale projects, everything is fewer than server-side, it will be better. But, whenever the application is small and it's easy to load to client browsers in a global environment. So, we know we don't need to use server-side rendering. So, server-side rendering can be used in React and Angular, but it will help only in large applications, large-scale applications. It is more beneficial for looking at our code and all things.

As for the security purpose, we are getting one issue. Awesome. The user has access to our AWS bucket. So from the front end side, we're directly using AWS keys for the bucket. At that time, we notified the user that they can get access directly from AWS and retrieve the key from the front end code. So what we did at that time, we created an API for AWS bucket uploading and for AWS cloud, and directly we are using uploading via API through the API. So we created a server in the routing web instead of being directly apart from the application side. That is our major error, like, visually.