Dilip Durge

Hello, I am, uh, bachelor of engineering computer technology in 2020, Paso. I have, uh, 12 plus years of experience, uh, in Java Technologies. I worked with CMS platform and as well as Java Technology as well. Here, uh, I why I applied this opportunity basically because, you know, after experiencing any Java technologies, I've worked, uh, you know, lots of different different peoples, lots of different different technologies, uh, not only on back end but also in the front end as well. I have, uh, more on, you know, back end experience. Uh, I'm working, uh, on Java, uh, Spring Spring Boot, Hibernate, and, uh, then Maven. And there are some other technologies like Docker. I have, uh, even, you know, working on the CICD platform, I have a little bit knowledge about the AWS. And, uh, yep. That's so

Yeah. Basically, you know, uh, while working with the microservices in the spring boot, so, you know, rather, I, uh, I give you my example. Uh, by working with the map like, this current company, uh, we have 2 or 3 microservices, which are, you know, sharing the same resource, uh, database resource. So, basically, you know, uh, we have a Kafka over there. It's, uh, you know, messaging tool. So by this tool, uh, we have configured the Kafka resources. So, you know, that can, uh, give us a, you know, proper way to, uh, you know, handle the microservices, uh, to, you know, get that whatever the resources they have accessing. So, yes, simultaneously, they can, you know, work on that, uh, resources. So, you know, we configure the Kafka. So whenever 1, uh, and microservice is, you know, execute some operations on or perform some operations on the resources. Then the Kafka is sending a message to the, you know, the processes. And the process, it's, uh, you know, uh, continue to, uh, that process. And later, you know, it also, uh, though another microservice also, you know, access the resources. And once it gives, you know, that message to the another another microservices that, uh, it's, uh, completed this process so that another microservices get that resource. And, uh, you know, the Kafka is not only sending the message, but also it's, you know, communicating, uh, between the 2, uh, microservices so that, uh, we can, you know, even, uh, have a proper way, a proper channel to, you know, uh, working and, uh, steps. And even we have, uh, you know, implementing some, uh, trace over there. So, you know, it's not exactly thread, but threads, we can use the threads. So, you know, we can check whether this our first micro resource resource is working, uh, done or not. So we handle this as well, uh, with the, uh, you know, with our program.

Okay. New York application. This screen box is a great job. Okay. So, you know, uh, basically, whenever we, uh, find the application, it's monolithic applications. So while working with the Spring Boot Microsoft architecture, you know, we are first, uh, try to check what are the, you know, areas which we can, uh, convert it into some mod modular or molecular layer so that we can have different different models to separate the compute application, uh, through which, you know, the compute applications can be run as per the previous work. So we, uh, you know, first upon, uh, dividing that, uh, all the applications in little, little, uh, monolithic or, you know, you can say micro parts. And then we, uh, try to configure or we're trying to, you know, implement the microservice, uh, for each serve each of the different operations to fetch what are the data are there and what are the data we need to fetch, to run a particular molecular molecular, uh, applications. We sure we are divided into different parts. So for that, we create, uh, rest applications, rest APIs. Sorry. Rest APIs. And that rest APIs, uh, we, uh, try to handle the old datas between front end and back ends. So after, you know, dividing into, uh, molecular parts, that application, uh, screen boot handles very, uh, you know, in a proper way so we can create a different rest APIs in your screen boots and microservices to, you know, not only, uh, handle the different different parts of that application, but also, you know, handles the in a proper way, basically, so that we can, uh, give us a proper result. So yeah. That's it.

What method would you recommend for securing this to restful in this framework application? Okay. So, uh, basically, uh, for securing rest of restful API endpoints in the Spring Boot application, I'm I'm recommending, uh, the auth or authentication, uh, services over there, authentications is there. So, you know, whatever the services are there, uh, or any URL. Basically, restful inputs, basically, URLs. So these URLs can be used by the front end to up front or to, you know, give us the give the, uh, client or when who are the users to access the resources. So we configure the, uh, authentication over there using a port or, yeah, auth. And by that, you know, we, uh, tell the system to ask for the role. If the administrator, uh, and the user are both are the different. So we are, uh, providing the basically, we are providing the role best for, you know, priorities to that risk pool endpoints. So only administrator can access, uh, all the risk pool endpoints, s, uh, to access. So we are, uh, as per my recommendations, we can go with the auth to secure the risk points.

How would the tune have on your session factory setting? Okay. Any high concurrent applications. Okay. So, basically, hybrid session factory, uh, setting, uh, you know, is, you know, basically, uh, to by using, uh, the concurrent applications, uh, we can provide, uh, it's, uh, you know, lazy, uh, in a way. So, you know, uh, while handling with the sessions, uh, so we can, you know, uh, give a particular sessions to a more not more than particular time or more than, you know, you can say the time required for handling a data uh, for a particular sessions. So we can restrict that session. Uh, otherwise, the poll applications is not properly working. So, you know, we, uh, we can, uh, configure the session factory, uh, to, you know, provide the create, uh, new sessions to each, uh, request simultaneously. And, uh, we can, you know, also using that, uh, uh, threads to give us, uh, the proper way to handle, uh, the, uh, player sessions to, you know, the risk request can access the sessions properly, and the sessions can be used properly, uh, in a manner so that, uh, the thread pool cannot be, uh, overlap or thread pool cannot be you can say, uh, it's not, you know, it's not giving, uh, to any bottleneck system or or there or something, they can easily access the applications out.

How do you plan processing patterns in screen application? Okay. Can I ask function to So, basically, proxy design pattern is, uh, not work more on the proxy design patterns? But, you know, uh, you can, uh, say, like, you know, like, suppose, uh, oh, like, uh, maybe, you know, as I, uh, said earlier in the example, uh, you know, uh, we can configure lazy initialization and, uh, you know, to, uh, access, uh, using the applications, uh, you know, simultaneously, uh, whenever it needed. And then, uh, you can also provide the, you know, access controls, uh, to the ensure that, you know, whatever the endpoints, uh, need to be, you know, accessed by the particular user of, uh, any which whatever the user needs to be accessed, that we can, you know, provide the access controls in the screen boot. Then, uh, we also modified this, uh, remote accessing, uh, for that endpoints. And, also, you know, uh, we can configure the log going, uh, so that we can, you know, understand what exactly is doing. And if any error occurs, uh, then we can find out where it's exactly the errors are coming from. And, uh, after you know, the most important thing is the casing, uh, in any applications. So that, you know, that can, you know, handles all the, uh, burden or all the load on the servers. So, uh, if we, uh, use the caching, then, uh, it will, you know, easy to handle the same request, uh, each and every time. Just whenever the request is again and again comes again and again. So there is no need to, uh, you know, accessing the servers. We can directly disperse the result of from the caching. So caching is also there. And, uh, as for the structure of, uh, the replications, uh, we need to, you know, creating the interfaces, uh, then, uh, modify it to some, uh, you know, the or our programs or or operations to, you know, to get or fetch the proper data simultaneously. So that also we can, uh, give us we can configure in this new application.

In following job, code block, uh, okay, an important principle of code oriented programming is. We can learn by the principle and explain the violation. Class rectangle with width, public width. Okay. And okay. If it enter blue, this type width, it can double. Okay. Okay. Override. Set width. Set width s 2.2. Alright. Set width 8. Okay. Then super set width 10. Okay. BR Super. Oh, so, basically, BR tag is there. So alright. Okay. And then so, okay, so, basically, uh, the error is, uh, means, basically, the violation is, uh, we use the extends, uh, class rectangle. Basically, this class rectangle, and we use this method, set width and set height. But we, uh, use annotations override over there. Actually, this is not the correct way. Uh, override is not required. Means annotation is not required over there, object of rectangular class because it's a class, it's not interface. If we say interface, then we can simply write public class where implement rectangle, and then we can override that meter. But as the rectangle is a class, the super class, basically, So we need to create the object of the class to access that method. So animation or write, uh, it's violation of, uh, the object oriented programming. Basically, we are extending, uh, the direct methods of directing to us, uh, but we, uh, write it, which we we wrote over there. That's override. So it's, uh, object oriented, uh, programming violation.

The Jaws mongering points and. Okay. Can you spell the issue that might prevent it from responding to the. Okay. Okay. So, basically, post okay. Slash. Okay. So, basically, it's the for in the first line, it's q s and here. Basically, the in the post mapping annotations, uh, we need to, uh, specify or modify that slash inside that single quote or double quotes rather than the outside double quotes. It's just an error. Uh, and next one's that we are clear. It's for body. Okay. And uh, for you, it is not working. Yeah. Right. So, basically, the first line, uh, where we are using, uh, in the snippet, that is the averaging post mapping. There, the slash, uh, is outside of the codes. It should be inside the single tool. So that's basically stop the, you know, or prevent the response to the current history test.

How will we join this framework application? I didn't check the password. It's seamless failure. I'm recording in the event of the system crash. In the event of the system crash. Okay. So, you know, basically, whenever we need to design any application, uh, so we need to know, understand what exactly the application is, the first thing first. And then, uh, as for the, you know, requirements, we need to gather all the requirements. So we need to talk with the stakeholders, business users to our clients to understand what are what are the, uh, you know, the requirements for creating any spud application. And as per their requirements, we need to create a we need to understand basically what exactly the user wants. And as per their requirements, we, uh, go with the, you know, application architecture. So in Spring Boot architecture design, uh, you know, first of all, we need to, uh, hand check for exactly the pattern we need to use. Uh, if it's simple, you know, form submission or if it's simple, you know, not handling any, uh, financial or any, you know, payments, uh, structures. So we need we can, uh, also, you know, collect these simple structures. So we need to first to, uh, understand what the design patterns we need to use. And, you know, in the application architecture, uh, the second thing is, uh, we need to understand how many, uh, basically, database, uh, is required or not. If there are lots of data that needs to be handled, so we need to use a proper database like SQL, MySQL, or Postgres. So it's it's basically based on the requirements, uh, depends on the requirements. So we can also, uh, check the data databases. And, uh, if we understand all the, you know, databases and the applications and program is which we need. So we, uh, basically, uh, while activating the screen boot application, we first, you know, has a a user, the interface, uh, like, uh, you know, the interface which, uh, which who who can, you know, handle all the request and, uh, to access the service. We also think about the caching service. We also, you know, think about, uh, the load balances to, uh, whenever we handle or whenever we need to multiple and simultaneously conquer to, you know, requesting access to the our endpoints. So we need to handle that one. So, basically, we need an interface, uh, a load balancer, caching server, for storing the data as the internal database. So these are the things we need to understand, uh, and we need to take care of the design in this remote application application, uh, to facilitate seamless failure. And you we also, you know, use a logger over there. So we can also use Kafka and for logging systems. So we can, uh, use the postman, uh, to, you know, check our database, uh, failure, uh, of with the endpoint. So we need to handle all the things, uh, while, uh, creating the sprint applications. So these are the things we need to take care of by creating the last remote applications.

The use of reactive programming is compared to traditional blocking meters. Frankly speaking, I'm not, uh, you know, working on the reactive programming. So I do not have any particular, you know, experience in the reactive programming in SpringBoard. So um, think let's skip that the questions.

What it is, uh, what it is for ensuring the integrity of a screen book? I think the systems communications or a mix of synchronous and asynchronous So, you know, uh, while, uh, ensuring the integrator of Symbloud Microsoft is a custom, communicating, you know, or a mix of synchronous and a single channels. Uh, we can use, uh, you know, there are lots of, uh, you know, messaging, uh, tools out there like Kafka or RabbitQ. Uh, so we can use, uh, that, uh, tools to, you know, communicate the microservices, uh, between each other. So, you know, we can handle, uh, their workings, uh, with the resources, uh, easily. And, uh, while working on the resources, uh, to and microservices, uh, is very, uh, good thing to, you know, communicating between the 2 microservices so that, you know, whenever the first microservices has some, uh, work on any resource so that another can, you know, uh, get a notifications that the DISMarker research is working on. So the same resources so that, you know, he can, uh, wait for sometimes or he can, you know, he can use, uh, any caching or something, uh, data. So that can be handled. So Kafka is I I know about the Kafka. So, uh, Kafka is, you know, a really good tool, uh, to, you know, use to between the macro services to communicate to each others, uh, you know, in our or the macro, whatever the synchronous and nonsynchronous charts. So whenever the request comes simultaneously or, uh, 1 by 1, so we can handle that can be, you know, using the messaging tools.