Sarang Goswami

So I have, uh, around 6 years experience in dotnet, and, uh, I have also worked in SQL for around 5 years. I also have knowledge of JavaScript, um, MVC, uh, a little bit of knowledge of, uh, s ASP, uh, Netcore. Um, I have also worked on various different technologies such as, um, Java, Internet of Things, um, and, uh, Oracle and even FoxPro. I have done my masters, uh, in, uh, computers, uh, and have always wanted to work with computers. So, um, I'm very happy, uh, that I got to work in the same field, uh, as my education. Um, besides English, I also speak 4 other languages. Um, so, uh, Hindi is my native tongue. I also speak, uh, Gujarati, Marathi. As I said, Hindi, and I also speak German. I was in Germany for around, uh, 9 months. So that's why I know German.

So, uh, we can scale the architecture in 2 ways. 1 is the vertical and one is horizontal. So what we can do is we can increase the, uh, resources, um, such as add more CPUs, add more disk space, increase the bandwidth. And the the other thing that we can do is, uh, we can create more instances of, uh, our application, and we can, uh, then manage that accordingly.

So the only way to manage a clean and consistent code base is, uh, we have to use third party applications inside Visual Studio, um, such as SonarQube, uh, and others. So, um, they will keep the code as per, uh, whatever, uh, options are available in, uh, SonarQube. And the second thing that can be done is, uh, we need to integrate, uh, SonarQube with our build pipeline so that, uh, anytime a build is created, the SonarQube will also run, uh, and it will check whether, uh, the code is as per the rules which are defined in that.

So, um, in order to optimize the application, what we can do is, uh, we can have some automated tests, uh, which can run on the application. And through that, we can monitor how the application, uh, how the application behaves. And if it comes to, uh, or rather it points to some particular area where the resource utilization is high or where the deadlocks are, um, occurring, we would need to go in and redo the code. And, uh, similarly, for cost optimization, if we see multiple hits are being made to the server, we can use the modeling and miniaturization. So that will reduce the bandwidth that we have to take. And the other thing that we can do is, uh, we can move out the um, or rather we can keep the log files, uh, size to a minimum and not log any unwanted data.

So the best way is, uh, we'll have several, uh, microservices created based on modules. So, uh, that will help us in breaking down the code into smaller and, uh, manageable chunks. This will also help in tracing out or rather, uh, it will be more helpful in pinpointing, um, errors when we, um, when we have issues such as high memory usage or deadlocks. That's how we can create the application.

Yes. We can always integrate c l d CICD pipelines for DevOps. Uh, in my current, uh, project, we are already doing that. So the way, uh, it has been done is, um, once the, uh, final pull request or we call it the release pull request, uh, is approved, and the build package is created without any errors. The we have a separate pipeline for, uh, deployment where we have to select what is the last build we want to deploy and on which environment we want to get it deployed. So, uh, it can be uh, done automatically as well as, uh, manually also. Like, when I say manually, it's just a matter of, uh, selecting which environment we want to get it deployed to, and, uh, then the process happens automatically.

The return value is not specified. Return type is not specified. And, uh, is equal to length. It should be length minus 1. Ar.length minus 1. Or maybe remove the equal to.

So we are storing the username without any encryption in the cookie, so we should not be doing that. And The password is also not being, um, I'm not sure whether this code itself gives us an encrypted password or not, but we should get an encrypted, uh, password.

So some basic things that can be done is, uh, uh, we should give proper names to the methods, functions, and business classes or methods, functions, and classes, which correlate to the business entities, uh, and the scenarios that we are planning to implement. Um, similarly, we can, uh, break down the code into modules and group together the business rules that need to be applied on, uh, different kinds of objects, such kind of things we can do.

Azure functions. Azure functions.

I'm not aware of, uh, repository and unit of works patterns. Sorry.