Tuhin Samanta

Sure. Uh, so currently, I am working with, uh, tech with IBM, uh, since last 2 years. And, uh, the project I'm currently working on just how the telecommunication company called MTN. So I'm working, uh, for their, um, back end, uh, things like managing their customer portal, managing recharges, and all. So it's basically created up with the Node. Js and the Loopback framework, uh, which is utilizing TypeScript. And along with that, it's using MongoDB and, uh, SQL based database as well. So before that, I worked in IBM internal project called IBM assets, which was a huge east west project. So and then before that, uh, uh, I watched in another, uh, project, uh, that was, uh, called Ulta Beauty Salon, which was a US based project. So it was, like, um, a complete salon system, and their their back end was created with Node. Js, Express, and PostgreSQL along with Redis and GraphQL. And for front end, it was used React and Redux. Uh, so my role was there a pushback developer, and I actively worked for, uh, both part. So before that, I was in another organization called the TechnipForce in. So when I joined the PHP, they were recording the service. So I used to work on their WordPress plugins and, um, WordPress plugins with PHP and with manual JavaScript and HTML CSS. Later, they promoted me as their PHP team lead, and I worked on their couple of SaaS based applications like Cloud Panels, uh, Course Panels, and uh, subfunnels. So which are basically the cloud panels, the prepared project, actually. So where it was, like, uh, people can create their complete website upload through drag and drop, like, uh, can create members and it's automated, uh, email, uh, autoresponder, and it used it, uh, was integrated with a lot of third party payment methods as well to, uh, you know, to automate it to sales membership and mailing. Uh, so it all all the things, uh, was, like, people can just install the software on the server and can, like, inter easily integrate these things through drag and drop. So that's the thing. And utilizing that corresponds was created, which was basically self hosted element system like Udemy or Udacity. And Shopify was a alternate to sub sub, uh, like, Shopify was a alternate to Shopify. Uh, it was also self hosted. So next to it, I, uh, moved to their JavaScript team. So my past project was a pursue app, which was a cold mailing autoresponder. So it was created up with Node. Js and Express and MySQL in back end and for content, And all the, uh, applications that, uh, I mentioned, they are, uh, most of the they are, like, uh, memberships used to be created and payments like that kind of places for customers who are purchasing was used to create with the React JS. And for application, main application, we used, uh, mostly, we have used Vue JS as well. So and and that was your well, like, password was a complete mailing autoresponder, um, cold mailing autoresponder so people can drag and drop and can put, uh, put make their sequence flow and all. So next week, we created a browser based on Electrum. So it's called Logi. So it was also

So MBVW strategy, I will be, like, using. So there will be, like, like, routers and their pages and they will pages will have, like, access to I will have different, like, a folder for my components where I will have individual component for my videos and the common, uh, components that I will have will be in a different, uh, trajectory inside components where Where I'll be using them on, uh, everywhere in in the common places on, um, like, other top other components. I will have a, uh, place for my storage. So store, basically, where I will have my Redux stores, and I will have my style. And there, again, it will have a structure provided by an engine CSS. So they are also directory based on common if they are that I have common, uh, in the CSS files, they will have us, like, uh, general directory. And based on other components and pages, I will have a proper hierarchy and will, like, store them properly, uh, on a different folder. So, uh, that's where, and I will have the n b file on my root and also the index file. So that's the thing. And my on my public there, I will be, like, storing my images and all even by maintaining the structure.

So, um, uh, we can use, like, a Jenkins or, um, like, you can, uh, use Jenkins, uh, for, uh, this purpose. Uh, so what it does, it, uh, like, it automatically, like, after put, uh, you know, like, pushing and after creating a PR when it's, like, got approved. So it's automatically does. It's all the things, like, uh, if there is any, um, it it does its Linde's, uh, thing. So it test them with the weather. All have proper syntax and proper, uh, good, uh, structure and then this and all. Then it can, like, uh, run the test cases itself. And once all done, it used to deploy itself, uh, into the specified place. So that's how it, like, used to it helps to go through a proper practice and, like, does the automation itself where the where, uh, human sometimes, like, can make mistakes. So it doesn't happen there until everything, uh, it's, uh, you know, working well, it doesn't, you know, deploy to. Thus harbor. So that's how it's, uh, process to go through, um, a proper practice.

So earlier, uh, we used, uh, the pattern, uh, for the back end application called the emission structure where we used to have all the models in, uh, one file. So, basically, they are, like, data, uh, or, database model. Maybe, uh, that may be a civilized database model. So, uh, that, uh, the things and the controller basically, like, um, you know, the controllers are like, uh, our our functional things that will merge and connect our route and and those and the models that I'm using, uh, so that's the thing. But nowadays, we don't have that view card. We use to create our separate application for, uh, view. So apart from that, what we used to do, if we are using our REST API and also we basically use routes there or API folder there and use your structure. Our separate API with proper hierarchy that's easier under a proper under a, like, uh, that is a parent um, uh, parent path. So that meaning that path, we can, like, create a separate proper folder structure and routes inside that. And if we are using, like, a GraphQL, so we will have a proper GraphQL folder and there, the proper structure again for individual elements and individual workflow. So I will have the proper structure. And there, we will have a proper folder for utilities, like, where we will have our helper concerns or the library files that, uh, we are going to use, uh, commonly. So that's the thing. And in the room on the room there, I should have a config, uh, folder. So config, basically, it's, uh, like, it's updating each hour in dotenv file. We can, like, specify, but the config file is the thing that where I can, like, stick to checking, like, whether all the things that I need, all the key are there or not. And program programmatically, we can modify that, uh, few, you know, keys and all if we need. So that kind of restrictions we can, uh, keep written in a config file. So in that way, even if there is something wrong in in v, so it forces us to go through a proper, uh, practice. And, uh, and for and for scalability, we can do one more thing. We can like, if it's a, like, programming perspective, we can, uh, for a large scale application, we can think of using cluster and, uh, that you will utilize the micro not micro, multi, uh, processing. And, uh, so so in that way, we can make it as, like, scalable. We can utilize the huge release there, uh, for our caching and all. So so for for collaboration, the structure, uh, structure and that structure, uh, in the, like, trajectory and code and, uh, you know, uh, folders are important as well. Also, the proper flow and it, uh, you know, just like I just mentioned, like, some places we may need to use cluster for proper relations, uh, proper when when we are using the, you know, database system. So structuring them properly using indexes properly, uh, connecting the the by probably, uh, to, like, uh, to make to, you know, make them visible proper. So there are a lot of good things that we can, uh, do there.

Okay. Uh, so virtual DOM, uh, is the virtual DOM is basically without using the, uh, either modifying or using the actual DOM tree. Uh, we what React is, uh, React is doing, like, it's take difference of a proper, uh, of a one DOM element when we are, like, uh, creating the root element. So there it sticks a reference there. And instead of modifying the entire document there, what it does whatever it doing so after, uh, when there's something state, it's changing when that, uh, props changing. So it relenders things and used to place in that, uh, DOM element itself. So it doesn't modify the entire DOM or it doesn't interact in that DOM team all the time. So that's the way. Now I can, like, explain how it works. Like, let's assume we have, like, a object that, um, that's the like, let's assume it's a React application, and we have a getter and setter and the init method. So let's assume we have, like, uh, inside init, we are going to take the parents through, like, the query selector or get element by ID part of specific, uh, element that, uh, I have, uh, that I want to report. So, um, now let's assume when when we are using a getter, uh, they are we are assigning something through git. So if that variable is, like, using in my content somewhere, so, uh, uh, I mean, in the into, like, the, you know, element that given, if we are, like, have content inside that, we can, like when we are setting some content, we can that we can, like, modify the take the h t in our HTML or, uh, it's a very busy example. So in our HTML log, like, it's, like, create up also proper DOM t even where the on which elements modifying, uh, I mean, DOM portion it's modifying it that just renders that, uh, portion in such a in such a reactor viewer. But for the sake of example, it's, uh, like, if I, like, getting a set, uh, set on there. So if there's something, uh, that I'm providing and it's the variable getting changed, so I can modify that variable value directly there, and it can do in our HTML. So, like, JavaScript, uh, in not only getter and setter, JavaScript has, uh, also now support a proxy. So with proxy, we can also, uh, do these, uh, things happening. So in such a application site, uh, React are reaching virtual DOM without modifying the entire DOM, uh, element, uh, entire HTML. It just takes reference of a variable and whatever we are, like, assigning things, assigning its, uh, child components or all are, like, working there. So all are, like, modifications and all all all are applying there. So this is your heart, uh, like, uh, how the virtual terms are working.

Uh, so one way, uh, like, uh, if it's a component level, we can use, uh, use effect to hook with the like, uh, it we to maintain side effects so you can, like, pass the additional, uh, array. So, uh, which it we keep it blank. So inside the only tool, like, get the content. Uh, it's only on time it will, like, trigger, uh, after the hashed agenda. So, uh, each actually, each time it renders. So I mean, each time it it mounts, so it will, like, it will be running one time, and we can use their page or Axios to, uh, call our APIs. And, also, you can use custom hooks of our logics that, uh, our that that API call that we are going to, uh, call multiple times. So if we use, like, a custom hook so that there it will, like, uh, it will give us benefit to hide our logic, uh, in one place, uh, one place and to, like, get benefits from other components. And another practice another thing that we can do, uh, if we are using Redux so that we can also use Thunk, uh, middleware. Also so in Thunk, uh, basically, the used to handle the asynchronous operations. So there, we can, uh, place our API call. And another place that we can do, like, uh, we can create our own media. So in our own media, we can also, like, they use to take the 3 arguments, um, does the the store and the next and the action. So, uh, when you are getting the action based on that, we can do our API call and whatever the values, then we can then pass it to our, uh, store itself. So that's, like, not practically used to, uh, that will it will doesn't do that, but that's possible. So there if we can, like, uh, when we get things happening, so we can, uh, like, pass that. We can modify the store from there or can, like, pass the payload to to the next. So it will also work. So this is the couple of ways that I've been sent. So we can So this is the way of asynchronous, uh, like, uh, data palletching. And, yeah, also, uh, obviously, it's a asynchronous start task. So every time we are doing, uh, API call or when the promise, uh, got resolved, so we, uh, huge. We need to maintain the state. We should update the state if it's in touch to suit, maintain the if it's a context to suit, maintain that. And, also, we should yeah, handle the errors to throw, uh, the catch person, and we can we should use a proper error handler that, uh, to handle errors, uh, as well. So, uh, that is a basically, a state itself, electric state manager, where you'll have error and whatever error happening there. So proper and based on that, I will show a different component that this error happened. So this is the way how we can handle errors in, uh, I'm sorry. How we handle our sync on a start data bridge.

So here, it's, uh, not maintaining the immutability. So what happens is, like, JavaScript object, uh, each JavaScript object, like, uh, used to it has the mutability thing. Like, doesn't matter, um, if we, like, assign it to a defined variable, and then we are still, like, modifying it. They are, uh, like it's, like, basically, it's, you know, modifying that variant object that, uh, it it has the reference. So in in the past case, what we are doing, we are, like, uh, completely getting a a new, uh, object there by spreading the these dot, uh, stated items. But later in the code, what we are doing so we just, uh, we are just modifying the items, uh, modifying the items just by concurring, uh, their the new item as an added. So that's the one problem. And another thing, there is also one key I'm seeing that a new item. So so yeah. So that's that's the thing. So it's not, uh, going to, like, we are not, like, providing any more this new item. So based, we could, like, spread it past the state and uh, then whatever, uh, we are going to modify there. So in that way, uh, it will be doing that, it will be a better practice to maintain the immutability. So in this, uh, code, uh, that's not working. So that's the problem. So what we could do, I we could, like, spread the, uh, the this set state and then spread the state passed. And then, uh, uh, inside items, I could, uh, take, like, Like, uh, uh, add in and then only the I mean, spread their, um, heat and could add a new item there. And, basically, there is a library called the human. Uh, so that, uh, it's also benefited in such cases to handle to maintain the immutability.

Okay. So here the issue which we are not assigning, um, we are taking the numbers and, uh, running the for each loop there. So now we are getting there as well. But what we are doing, we are not assigning that, uh, to some. We're just making the you know, inside this, we are just making the sum plus num, which is basically will, uh, do nothing. Uh, so what we need to do here, sum, uh, equal to sum plus num. So in that way, it would do the actual sum and or sum plus equal to, uh, num. So that, uh, in that way, it would give us the proper, uh, result.

So, uh, the best practice would be using a nonce. So nonce are basically, like, a a one time key. So whenever someone is rendering the application, so I will be giving her, um, giving up a proper token ID or a system ID so so that, uh, it only works all for that specific screen. And, uh, once that, uh, like, we can restore that in in a, uh, like, stored variable or maybe in a session storage. So when the the the whenever that that some will be going through the form, so that would be, uh, also passed there. And in back end, I will check that, yeah, whether it's, uh, if the system was created or, like, uh, if it's a JWT token, so whether it's a valid JWT token and it has the validity or not. And, uh, in that way, I can, like, uh, make sure that the the nonce, uh, the with that nonce that it's it's going fine. And, also, uh, what we can do, there are some way of, like, encrypt, uh, data. So in that, we can try encryption of our data. If it's a high volume data, we can, like, uh, break them into chunk and can consider them sending Azure. It's like a performance, uh, thing. So in that kind of business, we can consider that, uh, chunking. Uh, otherwise, for integrity, uh, maintaining the integrated token, it's one thing. And another thing that, uh, can be done is creating a proper session. Now this session are not using, so, uh, we can consider using a proper JWT token with the the proper, uh, expiry time so so that, uh, it's gets expired even though someone is, like, uh, doing copy the cookie from one browser to another. So it will not work. And uh, what else can be, uh, like, done each like, rate limited, like, uh, with a specific time, uh, that back end will only allow a specific amount of requests. And next, it will, like, stop, uh, taking the request or itself with the delay and, uh, take the request. And, basically, I think, uh, for when it's we are passing any data, which is, like, uh, which have, uh, to we where we need a high integrity, we can try that and and launch or or that token thing that we whenever we renders our bids, it automatically takes it from back end and can, uh, whenever you are making the request, uh, slice, uh, for the specific system, sending that token will ensure that it's coming from a proper source and will, um, maintain the integrity. And same, uh, for, uh, for the front back end, uh, to front end, we'll pass the the proper token and, uh, all, and we'll verify that, uh, as well. So that's the thing and proper with authorization and proper

Yeah. So, um, integrating part is like a a highly benefited, uh, thing. So it's like a, uh, two way, uh, like, authentication. So first of all, we just need to, uh, place at, uh, that whatever username or password, uh, they need. So, yeah, next to it, it will redirect them to, uh, with that to a specific server endpoint. So after that, it will generate some sort of token and all, and we'll authorize the request authorize the authentication request, and we'll again get back to that page with the proper, um, the proper JWT I mean, proper, uh, token that will expire since some time. Uh, and all the requests that we we send in and that that tokens will be, uh, using. So not only that, if we are using, uh, like, Gmail or other, uh, into other logging logging system, they also, like, maintain this flow in a very authenticated way. They they already used to have the, uh, the endpoint and all which you need to, like, whitelist. So it's in such a like, it mentions the complete, uh, complete security. Whenever you are making a request, it, uh, like, uh, taking the taking the token, it checks the validity and all. So this is how it's been updated.

I'm not sure about, like, this question, what it, uh, uh, it's asking, but if it's a performance, uh, thing, uh, so there, I will I if it's a if it's in the application level, so I should consider using, uh, like, for a high, uh, while we are doing lot of processes, um, and a lot of, like, users are using it. So from application end, we should do that. We would use, like, a system like to preserve that data which are frequently needed. And for databases and all, uh, from that perspective, I a SQL based database that I should using, like, index and also there are new database cache configurations available, so consider doing that. Whenever possible for long, uh, running data, I will be using, uh, try utilizing the worker threads and, uh, all. So in that way, I will like to try make make sure that, uh, the back end is always, like, available for to solve a request to, like, perform my content even when I am, like, solving, um, like, lot of request. Even if you select 1, we are doing some CPU bounding to the task, which takes a lot of time. So in that kind of this is cluster, it's going to help us the through, uh, multiprocessing. And, um, again, uh, that uh, that thought I mentioned, um, I will take care of that event event approach of React, including that uh, workers. So that will, uh, make our application, uh, efficient.