Shweta Patil

Yeah. Hello. Myself, Shanta. I have, um, I'm currently working as a application developer in EBD, and that is at of Sintech. My responsibility includes development of the type application of APIs, so not to plug in or a Spring Bash application. I have around 7 years of experience. And during these 7 years, I worked across different domains like banking, ecommerce. Uh, I'm currently working in logistic and, uh, a transport domain. I have experience with technologies like the JSP Subnet, Spring, Spring Boot, HyperNet, a a Spring batch. Uh, and, uh, apart from that, I hold experience with the relation databases such as MySQL and Oracle. And, uh, I don't have much exposure towards microservices, but I do work on few premises, and I have understanding of the solid fundamentals and how we can utilize things in software development. Uh, that that's all about me.

How would you implement the robot strategy of having a transaction in a distributor's payment application? Okay. So, uh, in distributor's payment application, we can use a programmatic and distribute a transaction management. So, uh, in my project, we have to use the, like, like, annotation based transaction management where we can annotate a method, uh, with the accurate transitional annotation. And there, we can set the propagation level, uh, the rollback. Uh, in rollback, we can mention the class name, uh, or the like, the class name or give them the new customer exception, which should be trigger on, um, in that particular transaction. And we can set the isolation levels and the time out as well. Uh, so using a transaction annotation, we can, uh, implement a role pass strategy for a full transaction and distributed, uh, Spring Boot application.

How would you do in hibernate session factory settings and have a current Java application? So the session factory is, uh, it provides, uh, application level of the session. Uh, so, um, it it the session type fields in creating the session object. And for the the the highly confident, uh, which are applications. Uh, we can create a session type of object which will make sure that the session object will be appraised. And I think by using that way, we can during the hibernate session, I think, I'm setting in, uh, on the end of this application.

In the distributed, uh, transaction, as I mentioned earlier, we can use a transactional annotation where we can save the I know, you know, a solution level transaction level as a a transaction or the transaction new transaction is safe. We can set it like that. Uh, the the rule back functionality we can set and the time out we can set using that way. We can ensure the, uh, asset property that is our domestic consistency, isolation, and with our BP, we can make sure, uh, that, uh, those assets properties are uh, being followed in another string of the application by using the transactional annotation in either the service layer or the database, uh, or, you know, data access layer.

Uh, so we have a low latency high throughput application. So in in that case, we can, um, go for the big plan where they can make a concurrent call that is a non blocking call. We can make our we can make our application asynchronous using enable asynchronous and, uh, asynchronous annotation on the method, so that multiple threads can, you know, move concurrently. And using that, we can design a low latency and high throughput job application.

Implement the optimistic, um, looking in this scenario. Uh, I think we can you know, all the entities which are, uh, getting access by multiple threads on that, we can save the log annotation by using a hibernate to achieve the optimistic, uh, lock frame.

Yeah. So there is a issue when it comes to the multithreading environment because, uh, the single time design pattern is implemented using, uh, the lazy initialization technique. So, um, here, we need to handle the synchronized translation by using a synchronized, uh, you know, method a synchronized block. Uh, so the most, uh, preferable day is using the synchronized block because it locks the minimum and won't be the required code. And it it it doesn't increase the waiting period of, uh, the other threads. So we can use a synchronized log inside this instance sequester transformers. Uh, and it will create, uh, instance on the when the instance is in the land,

I don't see any principal is getting any audited. It's all of the inheritance. Uh, method overriding. The only the thing I could see is, uh, using set width. Uh, we are setting the width as well as the height and using set height. We are setting the width as well as height. So using the width, we can set just the width. And using the height, we can just set the height. So I think that is I mean, the important principle will be, um, you know, I think the single responsibility principle that is a or one class, uh, should have a one responsibility that is not being followed. So I think that is the one we should.

What technique would you try to streamline crystal or classic? Okay. So, um, in my project, I have to use the screen batch, which is processing a massive data using the screen batch where we have to use a job. Then the job can have a multiple step and each step consists of item leader, item processor, and item writer. And, uh, it's processing the data in the, uh, in chunks. Like, instead of reading one data and writing processing and writing that, it is, uh, reading cross set of the data, processing that, and writing that. So, um, you know, so we can use Spring Batch, uh, technique, uh, to streamline the processing of massive datasets. This is bigger hybrid. Uh, I think it don't need the auto language here.

Test coverage for standard application, how would you go about how to do this with this for physical ideas? So I don't have any experience with testing. So I I I will have some time for this question. So

Uh, so for enhancing the security of JavaScript application, eliminating the external APIs, like, we can implement the spam and security using, uh, by extending a bit security from your adapter and enabling the bit security on that class. And we can override the configure method, uh, which, uh, can, you know, which can, uh, to which we can customize the security rules, uh, such as URL path and the rules, like the admin or the user. And, uh, also, we can override the configure method to provide authentication provider, type in memory authentication. In my project, I have used a in memory authentication. But apart from that, we can go for the JWT or or Okta implementation for the integrating the screen with security. Also, if we have our one resource on, uh, different origin and another resource on different origin, then we can handle the cross origin in our Spring Boot application by using that cross annotation and by providing the path, uh, in that. So I think by using these strategies, we can, uh, make others bring the application more secure.