Vishal Sehgal

I am working as an Node. Js developer at the back end in Accenture. I've been associated almost, like, 2 years in Accenture, and I totally hold an experience of 6 years. Uh, I worked on different domains like health, insurance, education, finance, etcetera. And I worked and touched almost all the cloud technologies like GCP, AWS, Azure. And I've worked on both type of databases like, uh, NoSQL and RDBMS. I also have exposure to third party integrations, APIs, and SDKs and also worked on different, uh, all the services of the clouds. And I want to integrate it, uh, with different data source, like Redis and Memcached.

So there were times in the in the past, like, where we have to roll up some you can say the APIs, So we develop and design APIs based on, uh, frameworks like Express. Uh, we also, you know, I also have exposure with GraphQL as well. So I have been working on developing these RESTful APIs. We also worked on securing the APIs using middlewares, securing the payload, basically, and receiving a specific payload. We also put some, Uh, you can see validations using GUI frameworks and multiple frameworks as a middleware. So that's all.

So, yes, I worked on, uh, all the type of databases that is SQL and NoSQL. So in SQL, like, I have mostly worked on MySQL, PostgreSQL, Oracle DB. And most most of the time on NoSQL, I worked on, MongoDB, uh, maybe DynamoDB and Cassandra. So this is what I have been worked on, uh, with different databases. I've also developed health based applications on MongoDB using CSFLE, that is client side field level encryption to, you you know, encrypt our database entries and to store them encrypted and to get them decrypted.

So if we talk about handling the front end and the back end architecture level of the application, it's like I work worked on both of the part talking about the back end. So we divide an application into model view and controller, 3 different parts of the application. And similarly, we have divided the front end as well into 3 different parts, that is model view and controller. So that is the best way and approach so that, you know, going further, we can, uh, you know, expand our modules, and we can, you know, work very easily in Teams, we can collaborate them. So that's the way how the standardization protocol works.

So in my past, like, I got a problem, uh, how to, you know, uh, in the COVID times, like, how to decrypt the records and to store them in NoSQL databases that we were using as a MongoDB. So we opted for MongoDB enterprises. And that time, like, version 10 was already prevailing that recently launched. And, uh, they didn't have the official documentation how to implement client side free level encryption. So that was the biggest challenge to, you know, protect our data, data entries into MongoDB Enterprise using CSFLE where there were no docs available. So that was the biggest challenge, how to Store the data encrypted and to get the data decrypted using the CSFLE of, uh, you can say, MongoDB 10.0 and above versions. So that was actually deployed by, uh, you can say, Health Applications. And, uh, you can say that that application is currently going and

So if you talk about the React JS project, like, uh, we can divide our application into user different life cycle hooks. And, uh, we can divide our application into model view and controller similarly. So So that's the best approach how we can, you know, divide our whole, uh, UI application, which we work in a React JS. Um, Yeah. That's all.

Most of the time, the challenges which a full stack developer faces is of API integration. This is the 1st primary problem. And primarily and secondary is, like, how to design the architecture of the project. This is actually the primary one. 2nd is how to integrate the APIs basically. 3rd would be how to, you know, uh, make our application safe and secure, both on the back end as well as front end, where to store those constants, uh, which are, uh, you know, deliberately stored in constant dot JS. Instead of that, you can use key management services, something like that, secret management services. So these are the basic three problems.

So the approach would be, like, all 4 problems which I have listed earlier, like, we need to define a specific architecture that is based on the approach of model view and controller so that, you know, the application is divided, is segregated, and categorized where the model is situated and where the controller should be there And then where the views should be there. So this will be the basic architectural issue that can be resolved very easily. And further, how how our application will be secured, how the data will be coming from client to server. And we also put some validations based on middleware. We also put authentication based on middleware so that our controller is not called all the times, uh, recursively so that, Most of the functionality, if required, are catered on the middleware level. So this is the 2nd part. And we can even implement, uh, you can say, worker thread make our application much more faster and having a better performance. So this is on the performance

So the, uh, the methodology like, uh, I have implemented worker thread in the Node. Js application most of the time so that, you know, the performance is much more effective. So what happens? Worker thread actually talks to the OS resources directly. And, uh, let's say, if you have a quad core CPU, that means 4 cores. So it can actually divide your whole application into 4 different threads. And if you can, you know, uh, like, if there is a request, which is coming to the server. So thread number 1 will talk to that request at one time, and 3 threads will be free. And if 2nd request comes, 2nd thread will handle. Similarly, uh, number of threads like t till n will handle, request till n number of requests. Right? So this way your performance of the application improves, and it becomes effective. And, also, there are methodologies like, Implementing authentication, uh, as a middleware and implementing validation as a middleware. Uh, the 3rd could be, like, you can, uh, you can secure your payload instead of sending plain JavaScript object. You can directly, you know, use base 64 or base 32 uh, formats of a string indirectly, you know, convert them and sending so that no plain passwords are sent from a client to server. So these are the basic approaches which I have done. The it could be improved. Like, the security part could be improved. Like, you can use encryptions at both the ends, private and public key so that to access and to send the data from client to

So in agile development methodologies, like, the best part is you come to know after each small deliverable of the chunk, like, was that delivered in a right direction? Was the requirement met or not? So this is the best part which I have experienced in my past of agile. And agile is, like, you know, in every iteration, you get a feedback so that you can improve. Right? So this is the best part of agile. Like, you get instant feedbacks and you implement those feedbacks. And at the end, when your delivery is ready or deliverable is ready, that is that product which is actually getting delivered, uh, will never face any issues related to the requirements, uh, or the, you can say, business logics which were to be implemented and which didn't implement. So this is the beauty of, you know, agile development that that's what I according to