Suraj Gaur

Yes. Uh, my full name is. Uh, I'm from, uh, Guropura. Uh, currently, uh, I have completed master from in 2019. Uh, currently, uh, I'm, uh, residing, uh, uh, and my other team is also Gugao Hriana. My current employer is, uh, Nomos Hitech, and the skill set that I'm using is your, uh, Java, Spring Boot, Spring Data, JPA, Hibernate. And, uh, for database management, I have used SQL Server and MySQL also. So these are the skill that I'm using, and I have a 3 years and 3 months of experience, uh, in the in the, uh, Spring Boot, uh, based web application. So, yeah, these are the this, uh, skill set and my experience related information that I do have

So, uh, for using, um, like, scalable data schema that support Hibernate's lazy loading and eager fetching strategy. So what I need to do, I have to, like, implement, uh, Hibernate along with the springboard application. There, uh, I can, like, use this to see, like, uh, fetching the data from the database. Uh, there's there can be, like, uh, many types of, uh, fetching strategy that can be used inside the spoon boot application through that can be used to, like, get the data from the database. So there's, like, some property of that can be, uh, directly used inside the domain, uh, the, um, the domain, like, uh, what the table it is using that database. So, uh, we need to provide the, um, uh, property, like, a face type face type property on a on a particular, um, the on a particular, um, phase of a table, or we can also provide multiple phase of the table so that it can be, like, used to use the strategy, the of the face type and retry the data accordingly whatever we have, set the property inside the face type. So it will, like, uh, there can be mainly 2 types of, uh, face type here. The first is, like, eager loading, and the second is, like, uh, lazy loading. So eager loading, what it does is just uh, um, when we when we try to return the data from the table and the property set it to, like, uh, eager, then what it does is just load the, uh, the main table data along with eagerly load the child data. It will load the child data at the same time. So what it does is take the time and consume, um, uh, memory also. And, uh, that's that that's why it's not a good practice, uh, when we, like, wants to, uh, use eager. That can be used with courteous. Like, we need, uh, when we need only, uh, all the data, then we can use the eager loading. Uh, otherwise, we should use the lazy loading. And lazy loading part it does is just, uh, uh, when we face the data in case of, like, lazy loading, it will just face the parent data. And then after, um, thereafter, we if we request for the child data, then after it will load the child data. Otherwise, it will not load the by default, it will not it will not load the, um, uh, child data. So in this way, we can, like, get the data, uh, in a fast way and less memory consume it consume consumption. So, yeah, this is the way this is the type that we can use, uh, for, uh, for, uh, fetching the, uh, fetching type of the

okay so for the best practices for implementing authentication and authorization in Spring Boot web application generally basically we used java web token JSON web token for implementing security so what it does is just it's just to take the authorization property that can be like it's destroyed GDLT provides authorization security like we can log in through tokens through tokens insert the application and can and can be a user can be like make it authorized there if he has a valid token what it does is just use a request to send to the application and the server sends authorized if the user exist then server sends authorized token then for the next for the next request of the client it's kind need to send the token along with this request so it will be like when it sends with the token send the request with the token then it will become as an authorized request so it will have a authority to access some kind of activity in the inside the application so yeah GDLT provide these these things and along with this we can use Spring security so Spring security does authentication mechanism do have authentication mechanism so that we can like we can have we can have or we can provide a user to authentication sorry not authentication I have reverse wrongly sent said some word here like authentication mechanism is used by GDLT and authorization is used by this Spring security so okay so user authenticated first user authenticated and then Spring security can be used to authorize the user to a particular rule or to a particular state to particular feature to be accessible by the user so in this way we can use authorization authentication in the Spring boot application by using Spring security and GDLT and also we can use OAuth technology like it is a built-in mechanism inside it like it uses internally GDLT as well as Spring security not Spring security but it uses the databases and the GDLT to yeah and it has a mechanism for authorization also so we can we can provide a rule there for a particular user and provide all the data's of the user inside the OAuth services so that we can like get the authentication of the user as well as authorization based on the rule whatever it is has assigned to the user so these are the best practices that can be used for making security inside the Spring boot application in accordance with authentication authorization

Hello! I am Marinette. Today,利久 문..... I will show you the highlights world of Here and Now. Notice the height difference in this world. Look at this. This is a person with a different touch. Moving from left to right, For creating reusable and modular components in a Java-based web application, the design pattern that can be beneficial to use inside the application such like builder patterns. Builder patterns we can use. We can also use factory patterns. The factory patterns. And also we can use adapter patterns. And there is also, by default, in Spring Boot application, it is also provided by the Spring Boot application. The design pattern is like... What is it called? Inversion of control. Okay. So, I am explaining one by one. So, what is like a builder pattern, what we can use here. So, builder pattern can optimize the... We can set property inside a model or a class dynamically. Like we can provide a specific property. We cannot have force to assign all the property inside the class, whatever it is defined inside the class. So, we have a flexibility to assign some property. Inside the class. So, we can use builder pattern there. And we have a scalable or dynamic property along with the builder pattern. And if I talk about factory pattern. Factory pattern is used for creating different objects. Different objects with the help of the factory objects. So, we need to provide some keyword inside the factory object. It will give us the related instances of the classes dynamically. We need not to like every time create different name of the class. We need to just provide some keyword along with the factory design pattern or class. So that we can get the required instances of the class. And in terms of like adapter design pattern. Adapter design pattern provides some flexibility of using the other APIs, other interfaces to adapt inside our application. So, it will also beneficial using reusable model components. So, what we like you do in adapter pattern. So, it takes the other interfaces, third party interfaces. And adapt our interfaces of the classes along with the third party interfaces. And we can use the services of the third party interfaces in our application. Without any contradiction or conflicts.

for for managing cross-origin resource sharing course in a Spring Boot application that serves a client-side application which uses JavaScript as a front-end technology for using the whole application so what we can do for course maintenance or course management we need to provide a property along with the controller of the Spring Boot application which is named as cross-origin security so there we need to provide the there we can provide a specific method name as well as some security keys along with the this annotations there is an annotation named as cross-origin so it takes the property like the types of methods and that some keyword like security keyword that can be specifically mentioned in the application property file and yeah these are the things that can be we need to provide inside the application the Spring Boot application controller in a class so that it will like act as a act as a security and manages the cross-origin resource sharing if the JavaScript application sends a non-mentioned request to the controller then in that case it will through a course error the application through a course error so so in that way we can we can provide a security inside the application as the other other other person cannot have not any idea about what type of request the Spring Boot application accept so it's providing a security and the only authorized person who know the authorized person or authorized client like front-end application who know what type of request it does accept and which keyword or which security keyword to use to like accept the request so it is the authentication authenticated client that can be request mentioned request to to the server so that it would it would be acted as authenticated as client and there could not be any possibility of reflecting course error and it can be maintained by other client it can be secured by other third party like other third user to protect from there from them so these are the strategy that can be used to manage cross-origin sharing

Okay. So, uh, there's a, like, uh, annotation. Okay. For, uh, implying declarative transaction management in a spring and we see, uh, application using, uh, Java's address translation annotation. So the Java's edit translation Java just brings edit transactional annotation is a magical annotation that can be, uh, used to manage the transaction, um, but we are going to, like, implement inside the application. So the entry transaction transaction notation is used along with the method. So it maintains it maintains the transaction of all all the transaction happen from from the application to the database and maintain, um, maintain a session, uh, so that it can, like, uh, it can, like, uh, roll back if any conflict inside the session occurs. So transactional attention is work as you like, um, if he wants to he finds wants to write a method, and there should be multiple multiple, um, uh, steps that need to be implement. Like, uh, we want to implement, like, update, uh, update data. Sorry. If we want to get, uh, we want to implement insert insert a transaction, uh, and I want to along, um, after that, we want to implement update transaction. And there's multiple of the transaction and then some multiple delete operation that we need to, like, uh, uh, do insert the method. So and it turns out very helpful for, like, doing these things and maintain the consistency of the database. So how does maintenance like, if, uh, in between of the, uh, in between the operation, whatever we were we are going to perform, so it does, uh, it does takes the it takes care of it does take care of the, um, in type of error occurred or not. If there is any, uh, error, uh, at the time of any operation, like, insert data or update operation, then it will rule back all the previous operation, whatever it has happened previously. So it it it does maintain the consistency and, uh, hold, uh, and hold, uh, sorry, and consistency and, um, yeah, this test, it does maintain the, uh, consistency so that it will not, uh, um, it will not make the data imperfect or unnecessary data should not be inserted at the time of any error. So, yeah, these are the thing that can be, like, uh, managed by translation annotation, and we can use effectively so that we can have a property of database. And, uh, yeah, we can we can effectively

Okay, so here what I have found here, okay, so yeah, okay, okay, yeah, there is one more thing that need to be like mentioned here. So first thing that I want to like, put some data here like, there should be a specific message should be mentioned here so that it can be identified by the client or what the wrong things it do, it done at the time of requesting the same endpoint. So there should be a message, a particular message should be defined here. So that it can be like, understandable by the client as well. Here all the messages whatever I find here, it is kind of like technical message that can be not understand by easily understand by the client. So we should take care of the message as well as we should take care of one more exception here. Like, it's there's like, you're not found exceptionally implemented and some exception here. And, okay, yeah, from my side, this is

Okay, so what I have identified in this entity class, the field like name and the price should be private here, because we have already, as I can see here, it is already getter setters are setted in after that in the blue line of course, so there should be there should be an maintenance of private accessibility. So, the name and the price field should be private here. So yeah, what I have identified here, the yeah, the accessibility, the scope should be private here, all the fields, whatever it is written inside the entity, it should be private, because we have already setted the getter, we have already written the getters and setters methods inside it. So there's no need of making it public. So it should be like private. And because of some security as well, because it can be like another security, but it can be accessible without making any. Yeah, these are the things that I need to like, put here in terms like it should be private here.

So, okay so designing a hybrid based persistence layer for enforcing strong consistency in isolation levels in concurrent transition, what I would try to use is like I will like create an interface to the in between the request and the communication layer, so what it does is just okay, so I will also maintain okay, so the interface I did I need to like create there in between the request and the communication layer, database layer, so it maintains the abstraction, it maintains the high level abstraction there and also what I will use, I will use session, spring session in case of like hibernate transactions, so I will use the spring session that perform the operation and along with that I will use try-catch block, so that if there is any exception occurs inside the try block, it will like cached inside the cache block and I will separately roll back all the transaction whatever it is happened in the try block and appropriately I will send the error message and the understable message inside the cache block, so that it can be like understand by the client and also I will maintain the final block, so that it will close all the sessions related objects of the driver related objects from other database, so that it will not leak the memory there, so for isolation and consistency, the transition is I think it is like best approach to use transition, yeah transition is the best approach to use or maintain the consistency and in case of isolation, in case of isolation there is not any I think there is not any separate thing that I need to like implement for isolation because database is already so intelligent that it can maintain the isolation by itself, so and I do have like I have not separately mentioned I have not separately mentioned any isolation type of maintenance there inside the code, so yeah these are the experience that I have like I do have to maintain the consistency as well as the isolation of the transactions, concurrent transactions and one more thing that I can use here for isolation, we can use threads that can be like protect multiple that can protect the multiple threads to occur the single resources, so we can use thread protected algorithm to maintain these things.

Okay. So for maintaining the, like, flexbox or creed, uh, and then an enhancement of, uh, enhancement of layout of string time leaf template. So and there is lots of flex CSS, um, of templates, screen tennis template that can be used to maintain the flexbox and grid in an a beautiful manner and then, um, like, responsive manner. So it it it can be used, uh, inside the screen put application for front end designing, and it can be effective in terms of responsiveness and and, uh, look wise also. So and, uh, the front end, uh, have not you have not so much used TwinTIMES templates here, but I do have used I do have used 10 limbs. So there this this library provides broad sectors, uh, for using CSS and designs and, uh, lots of, uh, CSS classes so that it can be make it beautiful and as well as interactive and as as well as responsive. So tail bound. Yeah. So the, uh, this leverage is very helpful for me that I have used in my, uh, projects. Uh, but in case of, like, time leave templates, uh, not I have not used a lot for maintaining, like, uh, uh, CSS, other things. I have basically usually I have used the basic, uh, CSS for maintaining Flexbox or threads enhancement. So, yeah, this is this is from my side for this

Okay. Uh, I just have, uh, um, easily to listed that that, uh, I'm like, my role is, like, developing back end application. It's more than that of developing the front end application. So I do have a basic, uh, knowledge about CSS 3 features and, uh, not CSS 3 only, but CSS features. And for making responsiveness interface using time leave template of Spring Boot. Uh, so I do not have a great idea about this one. So I have used basic CSS for implementing the grid or all the, like, response c interfaces for maintaining the checkbox, text input boxes, and, uh, the buttons, whatever it is, like, uh, and, uh, reflect reflect reflectively writing the text inside the and so on to the display concurrently. It is us it is basically the time I've done. So I do have a very basic idea on this one and not so much deep about this one. So, yeah, these are things that, uh, from my side. And for, uh, within the strategy to leverage the 60 features, uh, improves responsiveness, uh, I do have a, uh, very busy idea about this one. So, yeah, from my side, this one.