Vivek K

Yeah. Um, my name is. I'm a full step Java developer, and I have almost a 3 years of experience in a spring boot microservice docker. And, uh, I have completed my graduation 2015, my MC in 2018, and after I completed BA in 2019. And I have working in a GRAPS Technologies as a full stack developer where I'm handling the, uh, Spring Boot API, the main REST API, and the microservices, Docker, Angular. This is all the platforms I am working on. And, uh, I have, uh, more than many applications till now. Yeah.

Store the procedure will be the best way to perform, um, very efficiently. And the firstly, When we are working with the heavy data base now, when there is a lot of bulk of data set, the time stored processor is a way where we can work it out.

It is, uh, very simple. We can use a dependency validate. So we can use a dependency validate. Uh, validate dependency available in spring initializer just so we can copy and we can paste it. After that, uh, what we can do is, uh, in entity class, each column, we can do the validation. Like example, annotation, uh, max, minimum. Sorry. In column, instead of that, we can mention what maximum character, minimum, uh, direct nullable. This all our annotations we can use. Apart from that, uh, the best approach is in front end itself, we can do validation. And the back end also, we can do the validation. So that is a way to validate the user inputs based on each columns.

So so what we can do is, uh, in in, uh, that controller class, we can give the request cross origin, and that particular URL we can pass it. So whatever request are sent from the front end client from the particular URL only will be the allowed. Only it will be the takeable. Apart from that, it won't take.

Yeah. Um, globally handling means, uh, we can create a one global exception, and, uh, we can, uh, create what are things we want. We can use a throwable exception. Yes. We can use what the throwable we can create on throwable exception, first thing. Or else, uh, what we can do is, uh, there is a exception class. We can uh, implement it, and we can override that particular the method based on our need. So there is a exception classes there that when we can, uh, implement, then we can do the override. We can override it, and we can use based on our need. That is one of the way. Or else we can create one new exception, throwable exception. We can get a one new exception class for us, and we can implement it in our restful API.

We can use the spring security. Spring security is a from the initializer, we can implement it. And whenever we run the program, it generates a unique, uh, username and sorry. Username will be default to user. Password will be generated every time randomly In application dot property in application dot property, we can fix the, uh, static username and the password, but that is not the best approach. So what we can do is, uh, in, um, we can fix the username and password from the database. That will be the best approach and the best practice for the authentication on top. So whenever we run the application, it should fetch from the where the username password from the back end database and whatever username password we're typing, it should automatically validate with the 2 existing one.

So in this code, a direct column, uh, we are mentioning the, uh, column name for the each field in a table. So in that place, we have mentioned the name and we have mentioned the backslash instead of the double quote and also also. So that will be the wrong. It is not valid. So according to JP, it is wrong. So if you want to mention the default name, example, public string names there, If you want, that name must be the table, and then we don't need to mention the column because GPU automatically, uh, uh, it will define the each field name as a column name. So we no need to mention any slash and all. Here, we have mentioned the slash. It is a, uh, escape. We are using a escape symbol. So according we this according to it is wrong. So entity is fine. Correct. We are making product as a entity. ID, we are making primary key. Cannotation generated value are fine. It is good. So in a public string name and public big decimal price both are the wrong. Column name is wrong, and, uh, I'm not sure the big decimal ones we have to see. I'm not sure about it, but the the data type, whether it is existing or not, once I have to check it with it. And, uh, yeah, I'm not aware about I'm not sure about that.

uh um so because whenever we use the repository here fourth line private user repository user repository in that place we are auto wiring the user repository which is extend with the jpa repository so in that place when we use the jpa maximum we will use by only the id we will use only by the id so public user find user okay fine it is a function we have created so in that we are passing the string username actually username according to me it will it will be string so we cannot able to find by the username because it it will not be the unique it will not be the unique in case if you want to find we have to create a new class we have to create what sorry we have to get a new method after only we can able to do so here that will be the issue so it will throw the runtime uh error definitely because in a jp repository there is no any method find by username but yes we can resolve it by creating a custom code jpql is there we can create a with help of the entity manager we can create our own query and we can pass find by select star from table name where equal to where that particular username we can give so that like that way our own customized code we can get inside the method find username and we can resolve this error while um creating so we can resolve this issue yeah

Actually, uh, uh, I am aware about this question. I'm not sure, but, uh, they can use the transactions and, uh, we can use threading here, but the threading will not be the good way. Sorry. I'm not, uh, I'm not sure about this. Sorry. I have to see. I have to see once.

Very simple. In a there is a resource folder is there. In that resource folder, we can get our all the HTML file, CSS file, same. How we are getting same way that we can create. But in application dot properties, uh, we have to define the prefix part for our file. So and then that, uh, only we have to create this whole file service, normal HTML and CSS flexible. These whole things we make it. It won't have any that much difficult. Same as usual. Only in application dot property, we have to mention the we have to mention the particular path prefix path.

See, uh, when we're using controller and when you're using the return type, so controller annotation on the particular class, it will give the answer in a template form. Okay. So whatever, uh, written statement we are going to mentioning, computer computer will consider it is a web template. Computer will consider as a web template. By through that, it may it will, consider it is what is the web page. That is the thing.