Iram Sayed

Uh, yes. I am Iram Syed, and, uh, I have completed a diploma in information technology from Vidyalankar Institute of Technology. And then I was into BTech, uh, from from MS Abu Sudhak College of Engineering. In 2022, I completed my engineering. And in 2022, January only, I got selected in center of monitoring Indian economy as a full stack developer. So from 2020 to January, I started working as a full stack developer in center of monitoring Indian economy. And then in June, I was selected, uh, from LTI as a software engineer. Again, it was a role for a web developer as a full stack developer. So I eventually joined, uh, Larson and Turbo InfoTech. Then after that, uh, I worked in Larson and Turbo InfoTech for 2 2 years, and then I was selected in, uh, then I was selected in, uh, HDX. It is a remote job, again, as a full stack developer. So it's been 2 years 10 months I'm I'm working as a full stack developer.

Yeah. So while, uh, build, um, I'm working on I do work on such task on a daily basis. So I, uh, currently, I'm working on a CRM portal, customer relationship manager, uh, management portal. So on our dashboard, we, uh, on our dashboard, we have a business a business is related to businesses associated to more than 12,000 or more than 30,000 patrons. So I'll have to fetch the, uh, patrons' ID and their records on the dashboard when patrons tab is clicked for that particular business ID. So to, uh, ensure that the data is, uh, the data is, uh, fetched efficiently and there's no problem in fetching the data, I use async request and promise. And I use, uh, yeah, my, uh, I would smooth rendering. Yeah. And in React, we use reusable component for fetch, uh, for particular data to populate the data into a table. I use a re you use reusable component. I ensure that the less less number of lines of code should be there written for a particular functionality because I believe that when a code is written in it written in less number of lines and the less number of problems are created. So I believe that my code should be as efficient as possible. So, yes, I use React, uh, and Node. Js. So I we use a async await request to so, uh, using that, our data will be fetched very smoothly. And, also, I use I use efficient SQL queries. I believe that for a for example, uh, I want to fetch the data in such a manner that I want to fetch fetch it from 4 to 5 tables. So I, uh, I do not the one particular API will fetch the records of the stores, and another API will fetch the records of the, uh, order details, and another API will fetch the rec records of a patron. No. I would I would ensure that my single SQL query would, uh, give me all the details that I would want, and then getting by getting all those details, I would efficiently I would efficiently and, uh, integrate those query into my UI. So this is the practice I am following from past 1 1 or 1.5 years.

In React, what method do you use? Is a c g and mounting component that involve ongoing method. What do you say is essential for properly? Okay. So, uh, I believe that in React and when we are unmounting a component, we should ensure first, uh, the very first and basic thing we should use is a state update. And, uh, we should state update, I use a state update only. So, uh, yeah, when basically, for mounting and unmounting, I use state update. And wherever there's a there's no require state updates and logics, basically, state update and log state update plus logic. So whenever there's a need of a certain component, we we should render it. And whenever there's no need of the certain component, I just, uh, update my state to false or true. I give the flag and, uh, my component is, uh, unmount. Or, also, we can, uh, yeah, we can also cancel the request. When it is not required, we can cancel our request. And, uh, also, we can, yeah, cancel the request. We can update the state and then render a component base based on the logic. Uh, all these things we can do.

Your app's performance has degraded significantly as data. What did I would you take using React? I can't see. Filing. What the React app's performance has degraded efficient significantly, and data volume grew. What's up? Would you take using the React dev tools and MongoDB profiling to identify the solution? Yeah. Again, uh, so when our number of data increases so for example, for a particular business idea I'm having, as I said, we have 30 to 40000 rec records. So what we use is we, uh, the very first practice is that we, uh, render the data, uh, page wise. So on a particular page, we ensure that there's a in our API call, uh, the re record should go for a particular record should go for a particular data. Say, uh, say, in my API, I'll mention the page mention the page length and page number. Page length would ensure that my certain number of, uh, row data is only fetched, and page number would ensure that on which page I I would go. So, basically, using this logic, we should, uh, it is ensured that it is ensured that, I mean, uh, the data is handled nicely. So in API call only, like, uh, slash services, slash slash page, uh, page number and the page length. Oh, this is this is it.

Keep the React component state management approach. Can you explain what potential issues may arise, and how would it be improved considering best practices? This will be a constructive prop, Super prop. This starts to count increment. This is a yeah. This is this is a I mean, the increment count function, it it it it directly, uh, modifies the, uh, yeah, the count functionality, it is modifying the state. Yeah. It it is a direct this it is directly modifying the state count. You know? So what we can do is we can convert the class component to a functional component. Say, we can function component and then const count const count, and then, uh, we can leverage the functional updates. Says we can set the counter I mean, previous count and take the previous count and then count plus 1, we can take. And, yeah, all these things, we can use Yeah. This is a thing we if if it it gets come converted into a functional component, that then it would work more nicely, and then, uh, we can take a state for this set state. We can take a previous count n plus 1. Also, we can there are more, uh, practices like asynchronous, uh, request handling and and, uh, testing and error handling, try catch, or we can, uh, try catch, or we can also trig trigger toast in our I use trigger toast met triggering a toast toast message on my screen whenever there's a a break in my component. So this is a practice I use a lot. I mean, my most of the code, it has try catch if else. And, uh, if things are working properly, I show, uh, green trigger toast and with some messages. And if my function is breaking somewhere, I show the red, uh, trigger toast with some, uh, some error message.

Describe a scenario where an atomic operation in MongoDB is critical within a Node. Js application, and how would you achieve it? Describe where? Describe where? Okay. Yeah. So, uh, maybe use yeah. For example, yeah, for example, we have a we have our my the application on which I work is basically like a Zomato like a Zomato app. So we have order on board. Our food ordering app's name is order on board. So, basically, what happens is there's a a lot transferring funds and, uh, transferring between accounts happening and transaction through WhatsApp also we take. And, actually, this is not here. Uh, this is not the application for India. It is in Edinburgh, UK. So what happens is, uh, in our application, we need to transfer our money from one account to another account. So, uh, so this this operation then ensures the consistency and security. So what we do is we we use MongoDB's update operation. MongoDB's up update operation we use, and, uh, within our within within our our one of the variable, we we automatically increment and decrement the balance of the 2 accounts with a within a within a that within that particular transaction. So this is a thing we I mean, this is the most common practice we, uh, take into the consideration.

Explain a method to efficiently execute complex way in MongoDB that needs to read and write data in in Node. Js application. Okay. So, uh, we can use we can use we can use aggregation pipeline. So, uh, using aggregation pipelines, uh, to perform the big number and very complex data, uh, transformations and aggregations, uh, in a single database operation, we can use yeah. And, uh, we can use this method. So the and, also, we can use stay, uh, we can use stage based processing. I mean, we can, uh, break the complex queries into the smaller ones, and we can, yeah, as I said, we can use a query optimization. Actually, uh, we don't really work on MongoDB a lot. It we, basically, we work on SQL queries. So I mean, our we work on my database is SQL based. So, uh, what we and the very main thing we ensure is that our SQL query should be very efficient. I mean, I try that I try that the if my one particular page, it needs those number of data. And if even if that data is complex, I I make sure that my one particular API and my one SQL is only giving me most of the data. Data should be relevant. Irrelevant datas cannot be existed into 1 API. But when the data is relevant and then we should take, uh, all that data into 1 API only. And our SQL query should be as efficient as possible. So we have on Internet, we have an extension also to check whether our API is, uh, whether our SQL query is efficient or not. Also, on our, uh, I use MySQL workbench. On workbench, also, when our query is executed, it shows how much time it took and how optimized our query is. So that's that's a very helpful thing. And, uh, for Node. Js, obviously, non blocking asynchronous operations, putting async and await to avoid the avoid any waiting or any blocking in our code. So promise also we should use, uh, using promise or async await, uh, to handle. Async asynchronous operation is a very clean and, um, clean method. And, uh, yeah, that's it.

Examine the JavaScript function that is intended to return a new area with each element squared. Can you identify any logical issues or improvement that can be made? Yeah. Where square where I is equals to I s n, a r r y length, I plus plus squared, not push any. Yeah. So, uh, very, uh, it's the condition. So the loop condition, it is, like, I less than equals to area length. It will cause a problem and, uh, I mean, it is going out of bound. So it when I will reach the length of the array, it will, uh, basically give the when I will reach to the length of array, it will, uh, it will give the error because the, uh, array index is starting from 0, and it will go up till, uh, array's length minus 1. So and, also, yeah, this will give an error in square dot Less than 1. Okay. So array dot push should not be used because when our number of, uh, like, when our area length will increase, that will this will, uh, this will this will this is not efficient. Every time, for example, we have 30,000 elements that for 30 for 30,000 time, this whole, uh, function will work. So, uh, we shouldn't use array. Uh, I mean, sorry, push. So we can use, uh, I mean, change the loop condition to I I, yeah, I less than, uh, array length to avoid the out of bound. Yeah. And, um, we should use area dot map. Area dot map, it is a very common function. So instead of, uh, uh, yeah, we should use area dot map. Area dot map, uh, it will provide a more efficient way for, uh, our area to I mean, like, if you are creating a new area, that map is more efficient. I mean, even if there are 30 to 40,000, it will map in one go. So adding, like, pushing the element again and again, it's very hectic. And all what else can be done in this? Yeah. We can, like, uh, return array. Yeah. We can, you know, return array dot map number, uh, arrow function, and then num into num. We can use num into num. This is more efficient. And what else? Your try catch error handle.

How would you handle a data replication and consistency challenges in a distributed system with a Node. Js back end? So um, how would I use so in a single in a single masternode, uh, we could, um, like, simple data should be consistent. All I would say is that data should be consistent in all our system throughout our system. So, yeah, data should be Distributed system. There are 2 types of system. Distributed system and Yeah. In our distributed system, we can have, uh, like, all the all the notes should have same data and, uh, more suitable to I mean, large scale distributed system. So it it should have a like, uh, all the all our systems should have same data. Like, if our master system is, uh, like, our master, uh, multi master applications, we should use. So so, uh, we should work similar to mass master to like, how we have a master to master. So we should have a master multi master replication. So it allows us more flexible read, uh, read and write operation across our all the nodes. And, we should also have strong consistency. Like, all the nodes should have same data, but there may be delays and, uh, it is more suitable for a large scale distributed system. So yeah.

You are you are tasked with creating a feature that allows user to upload and process large data files on a taxi fleet management. Describe your approach to handle the file processing in a scalable way utilizing Node. Js and React. So, um, yeah, in React, we have a we we should I mean, we can create a yeah. In React, we can create a component with file input element that allows user to, uh, that allows user to input a file. Then we will use, uh, we will use event hand handler to capture the selected file. Then, uh, we you we will use yeah. We can use or fetch to send the selected file to the Node. Js in our back end server. And we can implement the processing, and we can, you know, store our data using put or post method. Uh, we can store our data using post or post or put method in our SQL. Then, uh, we can consider using, uh, I mean, we can consider using the chunking of our files to improve, uh, up or upload our readability more. I mean, it will ensure the performance performance and readability. Like, the if there's a large chunk of data, we should break it down. I mean, if, for example, if our p if there's a PDF file, so we can, uh, break down the PDF files into a PDF files into a character or we can break down into a page numbers. And then, eventually, we can, uh, store it into our database, in our into our table. Also, for file storage, we can use object storage. There's a, uh, object storage thing. So, also, we can use Amazon s three bucket for or, uh, storage cloud. Most probably, we use Amazon s three bucket for storing things. Local storage can also be used, but it is not more efficient. Storing on Amazon uh, storing on storing the data on cloud is more efficient. And for we can use asynchronous processing, uh, yeah, Asynchronous processing of our file. And, uh, for data processing, we should use, uh, your data validation must be done. For example, if we are taking a, uh, if we are taking image, then we should put a validation on our input that if it, uh, it should be it should be dot image dot jpeg or all these things. And if we are taking a JSON file, then we should also take a validation for a j JSON file. And, uh, while transforming our data, also, we should be very careful that it is getting transformed very correctly. Our basically, we can write a main function to process the data depending upon the type of function it is. And, uh, yeah, there should be and, uh, we can use a job queue system like, uh, to, uh, process the files asynchronously, which allows our, uh, which allows us for scaling and, uh, uh, if there's a fault tolerance that can also be detected. And, uh, yeah, data processing validation, all these things can be done.

When facing a when face when facing a project that requires a hybrid application, how would you decide using hybrid app development or React Native? Hybrid hybrid app development and React Native. So, um, basically, first, we should analyze all the aspects of our application that what kind of application we are using and what are the what are the things that is going to happen. So if if, uh, if our app requires extensive use of platform, like, there's a extensive use of our specific feature, uh, say, uh, camera or, uh, we are using notifications, then the app native, it can provide us better access to native apps. So and if our, uh, if our app, it is, uh, it it if it is maintaining a consistent and, uh, like, there's a cross platform going from here to there and switching into the, uh, apps, then also we can use this, uh, react native application. So, uh, also when, uh, when we should also also, we should consider I mean, there are practices that the organization follows. For example, if an organization is hiring people with, uh, MAN or with, uh, with MAN or with Angular, I mean, we should see if our teammates are, uh, expertise in more number of teammates are expertise in particular, uh, technology, then we should consider using them because that would, uh, that was that would efficiently help us creating a more, uh, efficient and more optimized application, obviously. So, also, uh, for a faster development, we should use HTML, CSS, and JavaScript. But if our application is more of a UI and, uh, if the application is more of a UI and, uh, less of a back end thing, then we should consider using simple HTML, CSS, and JavaScript. And, uh, but if our application is very big and it, uh, it is very it it is quite a complex, then we should consider using React as a front end and Node. Js and Express for a back end. And SQL or MongoDB, both are optimized, but most probably, people are using MongoDB, and it is NoSQL. So we could should go for NoSQL, obviously. But organization is strict upon SQL, then SQL should be considered. Yeah. That's it.

Could you demonstrate the use of CICD tools like Jenkins in streamlining the development process for a full stack project? Where is it? It is recording. I have not, uh, I mean, I have a very less number of time, uh, use this CICD into deployment thing. It is mostly done by our, uh, seniors. But I I since this is the practice that, uh, my, uh, very close colleague is, uh, using, so I quite I have a knowledge of it. So, see, uh, Jenkins, I mean, it is a very popular source. I've read, uh, it is used for building. So our code compile compiling and running test and generating the build articles are very takes place, and then testing, executing the unit and integration, and then end to end test can be done using testing and automation. And we have to set up a Jenkins. We have to first install the Jenkins and then configure it using our GitHub or, uh, we use Bitbucket. Bitbucket can be also used. We use GitHub. GitHub and bit Bitbucket are same only. My, like, very common. It is just a big bucket as a web platform, and it uses Git command only. So and then we can create a pipeline. So we can create a pipeline using Jenkins or or any other method. So we there's a build. Uh, we can we can, uh, trigger our code or push repository using the build. So there's a deployment happening. I'm I don't have much idea about CICD deployment.