Bhagwant Banger

Uh, well, I'm a full stack developer. I work on various technologies, including various languages for different projects. I've worked for the Indian force, and I've also worked with the JPMorgan Chase. Apart from that, I also had a successful career as a freelancer, uh, for 5 years almost. During that period, I worked with various JavaScript technologies including Node. Js and ReactOS. Please let me know if you have any other queries. Thank you.

Uh, that well, we will take into consideration the data model first of all. Uh, we will study all the entities, uh, as they are designed in the current SQL database schema. And after that, uh, we will consider the constraints of the database, and we will, uh, think about them and talk about how to put them in a manner that the constraints are not violated and the database, uh, database integrity is maintained along with the data structure that we initially planned and that existed in the SQL system. Thank you.

Well, coming to frameworks, I mean, it's really choice of the organization that I'm working with, what they've already adopted for specific system. And we can I mean, I consider and I actually advocate that the systems in place should be used, and we should go with the same framework that the company is already using because changing the things take a lot of effort and manpower and man hours, so I don't really recommend that? In case, uh, I have to choose or I have to plan a system, I would rather use custom build solution for building restful services. And if I do not have time or I have to take a fast track, I'll definitely go with Express. Thank you.

Well, uh, cross origin requests must be handled from the server side. If I'm using NGINX or Apache, Whatever I'm using for hosting the Node. Js application, it should be handled on the, uh, web server end. That's what I think. Nothing more than that.

Well, as I've mentioned in my application, my experience with the react dot, uh, dot j s is not very long, but, uh, I do prefer using functional components because that is what is being advocated in the community. And I really don't want to go with class components because I go with what the community really advocates because end of the data support has to come from the community. Thank you.

But I, uh, personally believe in not using the monolithic architecture. I believe in, uh, agile methodologies and where we can split the process, and I also consider using microservices instead of, uh, monolithic approach. Thank you.

Well, the user ID must be passed here, uh, while the Yeah. So the user ID must be passed here, which is not, uh, being passed because it is, uh, value which the function is dependent upon. Thank you.

Request dot wait.limit. The name and age should be, uh, separated by a comma.

Uh, I would go with hooks, the use state. And, uh, in case we are using Redux or some other platform, then I mainly reach those platforms. Thank

Then I will use a SVN, certainly, which can, uh, help in versioning and branching of the month stack project. Thank you.

Well, I think, uh, in a scenario where relationships are more important from entity to entity, the entity relationships are important, I would go with SQL. And if there are, uh, like, comparatively lesser, uh, or no relations within the entities. In that case, I will go with no SQL. Thanks.