Gaurav Singh

Thank you.

My name is Gaurav Singh. Currently, I am working in Temtec as a software engineer. I work as a Node.js developer. I work on three projects in this company. First one is creating a desktop application using Node.js, Angular, and Electron.js. My role was creating a desktop-based application. The UI part is taken care of by Angular, and the backend is Node.js. For creating a desktop application and framework, we were using Electron.js. What was the business logic in the backend? There were C++ DLLs like APIs. We need to call those through Node.js. The data will come from the C++ DLL. We need to throw it on the UI, on the desktop-based application. We have created this application for all the OSes like Linux, Mac, and Windows. We have also created a CI-CD pipeline for creating the package for that. Another project was creating a trading website, just like a trading journal. Trading journal means users do the trades in the past. We were having a visualization picture of that. That is showing what he did in the past. We were showing the pictorial of the last trader. We were having some graphs of what he did. He did loss or profit, so we were having some data on that. In the same things, we have added a chatbot API. He is having all the data which the user has traded. If he wants to get any suggestion from the chatbot, he can ask any question. Like what trade I need to do right now. I can do trading or not. Which company we need to buy the trade. Which stock market. All the things he can ask via the chatbot. The third project we have created is WebSDK. This is basically configuring the RFIDs devices. We are having RFIDs like project. RFIDs is a company which is creating the devices for the configuration of the devices. Previously, they were having desktop-based applications, but not web-based applications. In desktop, we can easily send the distributed features. But on the website, it was a difficult task. I have created the whole diagram and visualized a picture of that. We have created that. Right now, the business logic I want to talk about how we did that. But right now, we can also configure the RFID devices using websites. We are having WebSDK which we can use. We are creating a website according to their customer requirement. This is my side. Thank you.

So yeah, basically optimizing WebSockets connection in the full stack Node.js application involves improving performance, scalability, and resource efficiency both on the server side and client side. So there are some strategies we can apply on the optimizing WebSocket connections. Like first, limit idle connection. So what is this like set, like this is the part of connection management, like limit idle connections, set timeouts, or here based mechanism to detect and close inactive WebSocket connections and failing the source on the server. So and second thing like we can do like connection pooling. So what is this like reducing the number of WebSockets connection by reusing them, possible especially of multiple clients connections from the same machine. And other is like backup, other is like backup retry implement. So like exponential backup, the retry mechanism on the client side to handle any connection attempt in the case of dropped WebSocket connections. And like second one is like message optimization. So message optimization means like this bundle the multiple messages together into one WebSocket and frame an appropriate. This reduce the overhead of the sending multiple small frames and third one is the load balancing and scaling. So they are like, we also like scaling like WebSocket, like there is one like horizontal scaling. So use a load balancer, like there's some like server manager like NGNX and HAProxy and Apache. So with the help of that sticky session to ensure WebSocket connection are routed to the same server instance. And like another is the resource efficiently, like limit connection counts. We can add like implement a connection limit per user IP address, okay. And another is efficient data transmission, like send the only efficient data like instead of like entire payload, rate limiting and force the rate on the WebSocket message to prevent malicious client from the overwhelming the server of the exclusive traffics and like security of optimization. So we can add like SSL and TLS certificate on that, yes. So yeah, this is the basically things of connection, optimizing the WebSocket connection in the PlayStack application. Yes, that's it.

How do you manage cross-component? How do you manage cross-component? How do you manage cross-component? How do you manage cross-component? How do you manage cross-component? How do you manage cross-component? How do you manage cross-component?

%ah bro %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah %ah

How do you handle? So, handling the transitional operation in the node-based method and ensuring the data consistency and integrity, especially in the scenario involving multiple operations that must either succeed entirely or fail entirely. So in Node.js, this is typically done, the context database and support transactions like SQL database and no SQL database like MongoDB with multiple document transactions. So there are some steps like I am using for this. So let's suppose a SQL database like PostgreSQL or MySQL, so support transaction but out of the box with Node.js, you can use a PZ package for PostgreSQL. So like in this, we are having like some commands, some like SQL commands like begin, start with transition, SQL queries, execute inside the transition, commit, and this is a full transition to the persist, the changes, rollback is used to revert all the operations in the case of error, ensuring the automaticity. This is some example I am like explaining you with the help of that. So this is for the handling in transition in the MongoDB, like let's suppose I am taking you like database MongoDB, okay? So in that like MongoDB support like multi-document transitions from the version 4.0.9 as I understand, but it's required some replicas to the full transition support, transition in MongoDB works similarly to SQL database. And like example like MongoDB using Mongos and there are some, yes, this is the managing part of that and another like best practice to managing like use proper error handling so that we can use like exception handling, try-catch, and finally, and like we should keep like transition support, so managing work done within a transition, sorry, we need to use like appropriate isolation levels, like hit it, committed, and repeatable, like the serialization order and logging or audit, we can add like implement retry logic there. So and handling the transition across multiple servers. So this is the most tricky part. So like if our application is working with multiple microservices implementing like distribution transition become more complex. So there are some platforms like two-phase commit and like two-phase commit like Sega pattern. So these are the part of things while with the help of that we can handle that part.

The last steps. The last steps. The last steps. Ok. I do. I do. I do. I do. Restoration ok. Restoration ok. Restoration ok. Restoration ok. Restoration Restoration Restoration Restoration Okay. Okay. Okay. Restoration Restoration Restoration Restoration Restoration Restoration Restoration Restoration Restoration Restoration Restoration Restoration Restoration Restoration Restoration Restoration Restoration Restoration Restoration Restoration Restoration Restoration Restoration Restoration Restoration Restoration Restoration Mist messed Mist messed brackets Mist messed brackets Mist messed brackets Mist messed brackets Mist messed brackets Mist messed brackets Mist messed brackets So the method object is incorrectly structured It need to properly include the face data method So like let me explain all the fixes First is the data function So the data must be written in object Yeah, yes, okay Which is which in the in this case initialize data to null Okay In correct brackets, the closing brackets and the colons are fixed to the match the proper JavaScript syntax method object Like the method object now correctly contains a face data method which use a async keyword to perform the API calls asynchronously So this fixed version should have worked in intended where like face data can fetch the data from the API and store that in the data property That's it

I need to look over here. This is not... This is not... No. No. No. Can I give you a moment? Let me just... Let me just... Okay. Okay. Okay. There are some like... Like in Vue. Like... Okay. Like... Okay. Like... Okay. Let me explain from the start. So in Vue.js, Piano and StateStore functions are suited on a new instance of the state for each component or store instance that use it. So if a state object is directly assigned and not wrapped in a function, it will share across all instances. So this causes states leakage where changes in one instance of the content store effect another instance unintentionally. Okay. This is a correct like... Okay. So correct queries look like... Like... Like... Issue. Like... You can see it like... The state is already correctly wrapped in a function. So like there are some like... Logics and like... Yes. So let me check once again. Okay like this. So defining the mystore. Mystore part. So this is the PNS2 definition. Mystore is a unique name of the store. It acts like an identifier of the store across your application. Inside that like... Second argument. You can define the store state at sense. Yes. So state items like... State items inside that... Is an error. Like... The state is defined as a function written in the object. This is the key point here. By returning a new object. Each component or instance using the... Using this store. Will get its own dependent copy. And like... Especially the state object contains the property item. Which is an array initialized. Which is 1. Okay. So this is the key errors on that.

Okay, so basically optimizing server-side rendering application in nest or improve like SEO involving multiple strategies to enhance the page load speed. So first one is the metatag or head. Nest makes it easy to manage metatags like titles and other elements dynamically which are the critical for SEO. So ensure that like when we are creating the like managing metatag or head then ensure like that like you include the meta description canonical URLs and social media metadata like Twitter, Facebook, graphs, open graphs like and for better index on the sharing. So second is the lazy loading of the component. So improving the page load time by lazy loading components and images especially for content like the fold and yes the lazy loading components dynamically import the component to only load them when we need it. So faster loading speed improve like exercise like experience are the forever by search engine and which will positively affect your like our ranking. And optimizing page load performance like yes so page speed is crucial like a critical SEO factor in this SSR application optimizing the initial load time and can significantly like impact performance metrics like largest content largest content full like paid. And yes so and content footprint LCP, LCP like in NestJS image optimization use a like in this NestJS so image modules to optimization. So that we can like use infim like module there is a NestJS images so that we can like use for like optimizing that part and code like splitting. So this is the very important NestJS automatically split code into smaller bundles. So however to largest third party library take on necessary. Like largest third party library are loaded only when necessary. Okay and minify CSSJS like there are some minification like as we see CSS JavaScript files enabling optimizing options in the nest in the nest. So in that like we can use the NestJS to fully static page like hybrid board. So for page that don't need dynamic data use pre-rendering with nest generate command to generate static HTML files. This can be like greatly improves SEO since search engine prefers fast loading static content. So other we can use like you we can use like schema markup and it's like you can also like use like a mobile friendly design for optimizing that configure this assignment. So this is the part of the

Okay, so yeah, so benefits of using microservices, like there are many benefits for microservices. So microservices is allowing scaling individual services independently. Like Node.js being lightweight and event-driven is well structured for microservices. For example, like if certain services like user authentication payments require more resources, you can scale just that service without affecting entire application. So it will fail, so that particular service will fail. This will not affect the whole application. This is the scalability. Another is the modularity and maintainability. Breaking the application to smaller and smaller independent services leads to better modularity. So this makes it easier to develop, test, and maintain each service independently, which is crucial for larger and complex applications. And another is the technology-based. In microservices architecture, different services can be built using different technologies. While the core of the backend might use Node.js, you can write specific services like machine learning or Python, Java, or use high-performance services and depend on it. And fast development and deployment. So microservices enable smaller terms to work on individual services. So concurrently without conflicting with Node.js and its fast development cycle and vast package ecosystem like NPM, Node Package Manager, enhance the speed of the development for the individual services. Another is the fault isolation. Since services are decoupled, failure in one service doesn't bring down the entire application. As I said earlier, this is the improved life-flow tolerance. Each service can fail independently without cascading to other services. This will not depend on the other services. It will fail. So this particular thing will fail. This will not affect all the other areas. So easy CI-CD integration. So microservices are easy to integrate CI-CD pipelines because individual services can be deployed and tested independently with its fast startup times. Structuring backend for NestJS applications and microservices. When structuring the backend of NestJS applications using microservices architecture, we need to break down our application's several components like API gateway. We can devise our API gateway. After that, microservices for business logic. What is our business logic? Authentication, user management, inventory. And then after we can use APIs like HTTP REST and database for each services. We can provide the database for each services. Authentication JWT. This is the separate microservices JWT. So stateless based authentication.

Om. Om. Om. Om. Om. Om. Om. Om. Om. How to do... Om. Om. Om. Ome. Om. Om. Om. Aom. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Ja ja ya. Non-label. Aom. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om. Om.