Venkatesh

Yeah. Hi. Uh, myself, Vengadesh. Basically, uh, I'm from Telangana state. Uh, Yeah. I'm a I worked as a senior software engineer, uh, at Technologics Innovations Organization. Yeah. Overall, I have 5 plus years of relevant experience. So in that, uh, I have a a 4 plus years of relevant experience into a Python programming and also how our 3 Blaciers work relevant experience into, uh, Django framework, worked as an, uh, back end developer in, uh, like, a publication development life cycle. Mostly worked as in a back end developer on Django framework with the Python programming to implement the business logics and also, uh, to implement the APIs by using our REST APIs. And, also, uh, I used to work on a pandas library, uh, in back end side, uh, to implement few, uh, client based requirements. Uh, and, also, I'm familiar with, uh, front end technologies called React JS, HTML, CSS. And, also, I'm I'm familiar with JavaScript. I do I do have, uh, 2 years of relevant expense into, uh, MySQL, RWMS. And, also, I'm familiar with the AWS cloud platform. Uh, Yeah. Uh, mostly, I worked on automobile sector domain, uh, ecommerce domain, and health care domain. So my, uh, recent project is, uh, like, it is an EV charger software implementation. So it is into automobile sector domain. So there, uh, like, we do have 2 projects. Like, 1 is combo, 1 is back end portal. CPMS for charge point management portal. So in, uh, combo project, uh, we have, like, multiple microservices there. Few microservices are implemented based on Python programming. So I'm the individual contributor for those services. And, also, I worked on CBMS portal, so which is a charge point management system. So it is in a web application. Uh, there, uh, we implemented the, uh, web application with the back end, uh, with the Django. We used our REST APIs. Uh, we used Pandas library there. So, yeah, this is, uh, all about my short intro.

Yes. Uh, when we are, uh, reading data from the post SQL, uh, usually, uh, if it is in a web application, so, uh, we will follow I mean, by following, uh, by defining those database, uh, configurations in that particular framework only, we used to, uh, read the data from there. So here, uh, by configuring them in the framework. And after that, like, uh, as a properties means, uh, yeah, we will use, like, um, we will get only the required properties from that, uh, database instead of getting all the queries, all the data that which gear keeps, uh, more load on that, uh, loading of the data while reading. So, uh, yeah, I see properties. It it plays a key role, but, uh, we will get only the required fields by, uh, by using some, uh, like, uh, select the related, uh, free virtual related keywords inquiry set. So in this way, we can able to read, uh, the data from the post file SQL or from any other MySQL, uh, like, in we can optimize the performance while reading that query set.

Yes. When it comes to, uh, state management in React components, Like, uh, we do have, uh, hooks, uh, like, after year 6, React introduced hooks concept in functional, uh, based components. So there we have use state, use effect, and also we have context API. So by importing these, um, hooks, so we can implement the inheritance, like, uh, by using context API. We can, uh, use that, uh, defined, uh, state, uh, or variable in any, uh, component, uh, like, by sending and receiving that particular, uh, state by using context API. Yeah. It will place a key role to pass, uh, property to an other component.

How would you implement a catching system in Django to reduce the number of database calls for, uh, frequent queries? Yes. Uh, when it comes to, uh, Django, uh, there, we have a, uh, catchy mechanism. Uh, like, uh, we have types of catchy mechanisms in Django framework. Like, we have, uh, memcached, uh, management, and, also, we have local mem management, uh, file based catchy management, and also database database, uh, cache management. So if you want to, uh, like, if you want to save, uh, repeated request, uh, in servers I mean, remote server, so we will go with the name catch management by defining those configurations in settings file has, uh, catches, uh, in catches object. So we have to define that particular back end configuration with the location, uh, like, the port, uh, IP address. So this this is how we configure all the catchy managements in the Django. So if you want to save, uh, the repeated request of, uh, user in, uh, local server, then we will go with the local mem catchy. So if you want to, uh, save, uh, those request in any dictionary of a project, then we will go with the file based, uh, catchy mechanism. And and also if you want to save that repeated request or queries, uh, that which is coming, uh, coming frequently, we can also save them in database, like, by configuring them in settings file. So this is how we can go, uh, uh, like, implement a caching system in Django to reduce number of database calls.

Yeah. Uh, for demonstrating, uh, uh, building and optimizing a database schema in MySQL for handling of complex queries in a Django project, uh, first of all, we do, uh, follow the normalization concept, uh, like, um, that, uh, like, we do, uh, organize the data in a database in a proper way, uh, like, by dividing the complex query into the, uh, simple, uh, simple tables. And, uh, and, also, we can, uh, use a select related functional method or free fetch, uh, related I mean, functional method. These 2, uh, we used for, uh, while implementing, uh, query set, uh, like, while getting data from the, uh, database, uh, through RM concept. Usually, we use the, uh, select related, uh, method, uh, When we have a relationship, uh, foreign key relationship or, uh, one to one relationship, uh, there, we will, uh, go with this select select related method. So here, it will, uh, uh, get the required, uh, output in one query, uh, by using some joints concept. And, also, uh, if you want to get, uh, many to many to many, uh, reverse foreign key, uh, query sets, then we will go with this free fetched related, uh, method. So that is also to the same process, but it will won't use any giants, but it will we will get that query setting. In one query, only we will get the required, uh, output, uh, required query. So this is how we handle complex, uh, queries in a Django application.

So for describing a process to incorporate a Docker based development enrollment for a, yeah, Django application, ensure, I'll give you the prediction. Yes. Uh, like, not only Django, uh, framework. In any framework, if we are for example, uh, in Django application, while we implemented our app, uh, application, We have to create the, uh, Dockerfile. So how, uh, Dockerfile, we have to define Dockerfile. There we have to, um, create the services and the enrollment variables. Uh, the dependencies we have to write there. So with this file, uh, like, uh, when we deploy to, uh, a push to the any GitHub, uh, remote repository, So there while deploying by using this Dockerfile, so we can, um, make a build, uh, of all the dependencies by using this file, uh, without getting a further, uh, further, uh, description from the developer. So anyone can, uh, make a build, uh, by using this file, docker file. So this is how we can, uh, going to define that file in project layout folder, uh, I mean, project layout folder.

For the given Python code that involves restful APIs and practice, Django explained that code would be improved for better scalability and mainly. Yes. Uh, here, we have one class call item view, uh, set. So there, we are using, uh, view sets. Uh, so, usually, we use the view sets in class based view. So it comes with predefined methods, uh, predefined functions. Uh, there, uh, we here, we have one query that call items. We are getting all the objects from here. Uh, we are using model view set because, uh, we we have model class in our Django project. Uh, then, again, here, we he here, uh, they defined 1 perform, create a one, uh, of function. So there, we get the user, uh, information, and we save it, uh, to that particular database. So here, item dot object dot filter. Yeah. Here, he defined get query set to method, so which is a instance method. Here, he they are returning directly from the object, uh, based on the user. Uh, like, uh, we do have that in, uh, like, uh, auth auth, uh, we have get get user model, uh, default, uh, user table. So by taking users so in this way also, we can, uh, get the user from that object. So then after that, we can compare that usernames. Then after that, easily, we can, uh, get the, uh, again, we can authenticate that user. Then after that, we can get that user, uh, related, uh, objects, uh, items.

React as it's when it comes to rerendering in the following snippet. It's been why the component might not be rerendered when items are updated. So here, they are importing react use state from react module. So they refined a function call item list, uh, function component. Uh, items, set items. So add items also, one handler they kept. So here, in return, a new item, add item. So here, uh, because it will use a virtual DOM, uh, so that's why the required, uh, updated variable are only going to re renders here.

Yes. Uh, in NextJ's application, leverage your increment status, uh, regeneration to improve the performance of your content updates on the news portal. Yes. Uh, like, um, this is a new concept, uh, for me, so only I have general knowledge on this.

Functionality with filters and full text search capabilities in Django. Yes. Uh, in Django, uh, for implementing advanced search functionality with filters and full stage search capabilities, uh, like, we do have filter method, uh, inquiry while defining query sets usually from objects by taking the filter method. So there, we can, uh, we have a number of conditions, like, uh, whether the particular variable, uh, underscore underscore, is contains, uh, icons, which is a in case in case sensitive, and also greater than less than, uh, uh, underscore underscore in conditions, we we can implement. And we can also use the values method also. As we as I told that, we can also use selected and abbreviated. These all we by using these methods, uh, we can, uh, implement the advanced search functionality in Django application.

Could you outline a method for integrating a Python based machine learning model into a Django back end for real time. Yes. I prefer that, uh, Python based mechanism learning models into a Django back end for real time predict predictions.