Kajal Rana

Hi. So I am a back-end developer, working in more back-end mode using a JavaScript framework along with a MySQL database. I'm having work experience of 5.2 years. And I have worked with several other back-end technologies, including NetJits, databases like MySQL and MongoDB. I'm working at my current organization, Bajaj Finserv Health, which is situated in Pune. And I've been working with Bajaj since 2021, and I'm currently working in Bajaj itself. Previously, I was working with AmStaff Technology, which was situated in Bangalore. And the technology stack used in AmStaff was AWS and AWS services. And I graduated from a college in Zurich in 2019. And I completed my internship in Zurich itself. And the company I interned at was located in Surat, named Logic Point. I worked there for 2 years, having worked on various dotting projects.

Implementing a middle map for rate limiting. So first, rate limiting is to limit API calls within a certain amount of time. A middleware can be integrated to rate limit. A middleware is something we can access the request and update the response. So we can write the middleware with a reality meeting of 10 seconds per API per file, and we can mention the endpoints. We can attach the middleware to those certain endpoints itself, as middleware is plug-and-play kind of thing.

Indexing means that the index of how the search queries work is the query will scan the whole table if indexing is not done to search the required data. And if indexing is done, the query will target directly to the indexed position of the data. Hence, the query, the search query, or the simple query will be faster than the query which is running on a table without an index.

To prevent SQL injections in the NodeSource application, we can use SQL string package, which is available in NPM. It will stringify the data, will not allow the registered keywords, and it will prevent it from SQL injections. So SQL string package will be helpful. Plus, there should be some validations on the parameters that are getting fetched from the API call. Validation should be, like we should not allow special characters to result words, like select, update, delete, in, and in the parameters.

We can use Kafka to use the real-time updates as it is an asynchronous function that it works on. So Kafka will be the best approach to use real-time data updates. Plus, we can use Azure Service Bus to update the data in a MySQL database without getting without keeping a load on the database.

I'm not sure.

In this, we can optimize NPM install to NPM install hyphen CI, which will install only the necessary packages and the others will be used from the cache. And instead of copying packages, copy dot to dot will work, so we can remove the copying of packages to the directory. Hence, the optimization of two stacks will be done in this.

To guarantee the asset property, we showed you a transaction. A transaction is something that I've used in MySQL queries, and MySQL query uses transactions to commit and rollback. The asset property can be achieved by using commit and rollback. Commit means all the operations are successful, and the transaction will not commit the changes. If any one of those fails, it will roll back all the changes, and nothing will get updated in the database. This will restrict partial updates, and we can achieve the asset property using database transactions.

We can create an environment file in the Docker file itself. So, we can use Key Vault to store the sensitive data in the dockerized environment instead of keeping it in the code base. We have to configure Key Vault in the code base, and we can access the keys from there. But so that we cannot directly add the data, the key and value of the sensitive data to the code base. So, the key is the answer for securely storing sensitive data in Node.js and Azure Blob Storage.

So there is something called AWS, there's something called CloudFront where you can monitor the performance of the application by the logs that AWS will provide. Plus, we can manage traffic by load balancing. And, yeah.

So CICD is continuous integration under this deployment. For the benefit of using CICD is we don't need to always go and deploy the build manually. If CICD is integrated, any code pushed in the target branch will automatically start the deployment in the containerized environment. CICD is very helpful in the deployment where you have a large number of teams and many deployments. We can set up the deployment using Docker or Jenkins or Kubernetes to automate the process.