Neha Bhavsar

What about your background by the end of the business production? Yeah. Sure. So my name is Neha, and I have around 8 years of experience as a full stack developer. So I have started with the back end developer first, and in that, I have experience with Node Express framework, plus I have also experience with Nextiva's framework. And in terms of a database, I have experience with the MongoDB, PostgreSQL, DynamoDB, and also MySQL. Besides that, I have also experience of working with the front end technologies like Angular, React, and Vuzage. And besides that, I have also experience of AWS services like Lambda and, uh, state machines and, uh, API gateway to start up development services and also few deployment services like, uh, AWS EKS, AWS ECR, or AWS ECS. So that's sort of about the might be.

Yes. The method will implement item potency in the list full APIs build with the the method will implement item potency. So useful API is filled with it. So regarding the list full API is built within the node. Js, we need to, uh, we need to define few methods of, like, let's say, get, put, post, which methods we need to define, and we might need to write the business logic based on our requirement to, like, what we need to pass the data into the post below or what would be the validation layer. So those stuff we need to define.

Deciding between REST and GraphQL for a node based projects. So that depends on the project requirement, which type of structure we need to go with either the rest or the GraphQL. So GraphQL is mostly very, uh, easy to and easy, and, also, it is straightforward to implement. So in terms of a straightforward, let's say when we have some specific data which we need to get, and there are some specific results we need to get from some APIs there. And from there, we just need to pick few columns or few keys which are returned from the response. Then definitely we should choose for a graph QA. And if there is some custom requirements we have, like, we need to upload some files and we need to put some data and we need to, uh, third party. We need to put some data into the 3rd party or we need to execute some wave hooks. Or let's say if we want to send email or, uh, particular SMS type of stuff, then we should go with the rest API.

Configure a postgreSQL replication strategy to improve the phone tolerance of a Node. Js application. Okay. So regarding the replication strategy for a postgreSQL or a vendor database, let's say, if we, uh, there should be there will be always a one primary and there will be can it create a one replica set? So how primary and replica set will be configured and it will work? So let's say whenever we want to write some data into the database and, parallelly, we also want to read some data. So at the same time, we can write some data into the one of the copy. Let's say there is a primary copy of the post process here. And at the same time, we can use the replica to read the data. So we their particular both edit, uh, both operation won't conflict with each other, and it will block or lock the database at the same time because read operation might be sometimes heavy to read. At the same time, write will take some time to write the data into the database. So both should not be block each other.

Setting up a continuous integration workflow using the CICD for an area. Yeah. So but creating a workflow for CICD tool for a Node and JS application. So first of all, we might need to define like, let's say, there might be some steps we need to to follow. So for example, if, let's say, we are using a docker container for our Node JS application, then we need to write our steps in in particular, uh, CICD workflow. Same like, let's say, create a build whatever the code we have. Create a build for that to include the docker, then create an image for that. Then we need to push that image at either we have some docker registry or if we have some elastic search registry. So we need to write steps in our workflow to execute those steps. So we we have some speech specific, uh, technical jargons which we can write into our workflow files. Let's say, either we are using data, so then we have to we need to stick to that particular, uh, terms to provide. Let's say, first create a build and, uh, upload that build to the registry. Then after the registry, uh, we upload the build. We we can also define, like, if there is some code push to do this branch, then execute this step. If there is some code push to do this branch, you could, uh, execute these steps. And based on that, there will be some, uh, commit tags which we are going to get. So we can attach that text to the like, our registry, uh, particular tag. And based on that, we can define, like, which environment should be restarted or which particular instance should be restarted based on those CICD pipeline.

How do you mention both read and write scalability for a postcode as well as a bridge in a high traffic environment? Okay. So as I mentioned in a of the previous question, like, you know, if we want to if we have a heavy read and write operations and we want a scalable operation and we have a high traffic, then we need to keep the, uh, replica of our post case instance also. I mean, that we can choose to define, like, whenever there is some right operation and the parallel delete operation is happening, then we can use 2 separate replica or 2, 1 primary and 1 replica copy to, at the same time, write something into the database and read something from the database.

In this Python code that uses Flask, a common design principle is being wired. I can explore and explain. So here, one of the things which I should, uh, suggest is that there should be one validation layer which should be there. Either we can use a middle there to, first of all, to authenticate the user. And if that create user is some registration functionality or whatever, then there might not see the validation layer for that. But for fetching the user details, there should be validation layer. Uh, I mean, authentication layer and another one is a validation layer. It should be there for fetching the

So here, what I find is we are not using the body parser or anything to pass our body data. So that should be 1. And also, there should be one of the middleware to, uh, uh, authenticate, uh, requests. And if that is not required, that might be optional. If this is the public cloud, then that should be fine. But in the other scenario, there should be a body cursor to pass the data. And, uh, there should be some chorus, uh, configuration also needed if it is going to be used or consumed by some, uh, another, uh, host.

High throughput system using postcode SQL to handle 1,000,000 of transactions per day. Okay. So if you want to handle a millions of transactions a day using a Node JS and a PostgreSQL, then first of all, our Node JS architecture should be designed a way, and also the PostgreSQL should be defined, uh, with some more replica and also with the more configuration, like, as a same time, there might be some heavy traffic. So we need to handle the throughput with, uh, accessibility, uh, allowed accessibility. So in terms of if, let's say, we think about the Node. Js, and Node. Js should be secured in highly scaled application if you want to allow the traffic high traffic.

Implement to optimize the cost cost of cloud resources for a VHS data paper. Automancers will be implement to optimize the cost of so when we deploy the real test application, it depends. Like, are we deploying the static bills? So if we are deploying the static build on a cloud for that form, so let's say if we take example of AWS, then I if there is a static build, we can deploy it to the s three, or there should be some light cell instance we can use if that is not a state Let's say, if they know we are if we are using exegesis, So there might be server side deployment and required. So at that times, either we can use s 3 light cell or if it is, uh, like, server side, as I mentioned for an s s, then we might need a VPS. So if we need a VPS or else we go for AWS, VCS, or something, then we can define our task definitions, like how much requirement we have, how much traffic is going to be there, and based on that, we can define our task, uh, number of a task. That way, we can, uh, you make the cost effective applications I mean, cost effective deployment.

TypeScript into an existing Node. Js project and what benefits would it be? Yeah. So, uh, TypeScript itself has so many benefits. Like, we can define our linting errors. We can, uh, check some, uh, type of variable declaration errors and so many there are TypeScript providing us a benefit. So in existing Node JS application, first, we can, uh, install the TypeScript model. And based on that, we can upgrade our files to use the TypeScript. Like, first, we can, uh, update our request statements to import. And based on that one by one, we can upgrade our packages, and there are also some third party allows. Uh, other third party libraries, uh, available to directly migrate to the typescript. We can use those.