Ishwar Bhat

Okay. I'm a soft passionate software engineer. I have total 6 plus years of experience. Uh, mainly, I work on web applications As well as, um, like, delivering them end to end. So, basically, I, um, my main technology tech skills are Python, Django, Uh, and then, uh, I'm comfortable with AWS cloud. And in the front end, I am comfortable with React JS, JavaScript, And, uh, the React JS next next JS framework. So, uh, I worked on various web applications, Uh, where, uh, we have used the rest APIs also. We can integrate with the, uh, front end. Also, uh, we I'm experienced, uh, in, like, uh, running scheduling jobs. Uh, if in a web application, you need to run Chromes, uh, like that. Also, I'm experienced with, End to end deployment, like, creating CICD pipelines, uh, hosting the web application in the Elastic Beanstack, Uh, in AWS, uh, managing all those stuff. Uh, also, I'm experienced in managing a small team also. I have, uh, handled, Um, group of developers with, uh, group of 10 developers. So I can lead, uh, the team also.

All of asset properties in Postgres. Asset properties, I'm not sure.

Python libraries, commerce. I'm not sure. Maybe Pandas, which will be which is great for handling Excel's data frames. Uh, apart from that, we can use matplotlib if you want to plot any graphs or anything.

Node. Js. Server side Node. Js. Mostly, uh, I I use only Python in the server side. I have never used Node. Js as a web server, but Node. Js, Like I said, uh, I am only comfortable with the front end part. So, uh, I noticed We can just create models in Django as we created Python. We can create models and, Use ORM and stuff on direct David queries that will help us choosing the engines later also. Um, first, like, we need to use the rest APIs in the server and, uh, you like, no HTML editing at all, just the rest APIs, integrate some authentication, the rest APIs. Yeah. Create the app accordingly if, uh, we are using Django, uh, as per the use case.

Python framework, uh, for server side logic, we are largest quote in Django. Uh, thing is it's very flexible, And it's very efficient. You can write on the logics quickly. You can clear the projects very quickly. It provides all the security and all the frameworks for REST framework, uh, using REST all the REST API framework. Uh, so if you use Django REST framework, uh, by default, security and all taken by Django only, like, x frame, all those, whatever is there. So, uh, REST APIs, you can easily create with, uh, Django REST framework, uh, and you can manage all those settings and all in one place. Uh, and, like, if you want more efficiently, like, uh, Django querying is through query sets. So that, like, One time on next, you run less. You will actually use it. So it will be very efficient. So, uh, like, uh, if you want more customization, like, writing very easy. But if you want more customization, you can execute also using, the Django framework. And, uh, if you want to use it as a, uh, like, in the Anyway, in the server, uh, it's very, like, scheduling jobs and all. It's very easy. But if you want to use it in, Uh, in the front end, Django template model is there again. So Django templates are very easy to render. So that will be very easy.

We'll temp on data processing means we can do it in lot of ways. The good way would be, uh, with the event based triggering. So if something happens, so we subscribe to that event. And, like, uh, data changes, we get even so we can handle the data in Python through various it might be web webhook Or, uh, apart from event, if you want to do, we can do it in jobs. So where we schedule jobs and, uh, it will process the data, uh, once in a while in regular basis. Or even there is there are options, like, based on the it will pitch clearly depend on what kind of problem you are solving. Sometimes you might, uh, prefer Redis, uh, if you want to, like, you know, handle the, like, uh, WebSocket kind of thing. So we can go with the, uh, Redis or RabbitMQ that cache memory things. Otherwise, we can use SKS, like, uh, if you are your assist kind of and the problem is kind of solving the work best. So I want to do this work. So there is a work, so I can put in the queue and my worker queues can work on that. So depending on the problem, um, we can proceed with

Okay. If you want to set use singleton, basically, this is my TV connection, And, uh, connection should happen only once. That's what, uh, usually, the DB connection should happen only once, Um, because if you have more connection, it would be, like, more upload on the server. So in the init method, So assuming we have time to implement. So, like, uh, I would make this, uh, class instant, my DB connection as singleton class. Singleton in the sense, only 1 instance of this class can be implement created. So even if you create more instance of this class, it will be only 1 instance. It will be still pointing to the 1st instance. So I'll implement the singleton. So we there are a lot of ways you want to create singleton, my preferred way is, like, uh, overriding that in it, uh, new method. So in that new method, we can just pass in the object, and we can make it as singleton. Uh, you can use meta classes also. There are there are a lot of options, Basically, to create singleton, uh, you can order the new method and easily do that, uh, singleton. Uh, then after that, uh, uh, so whenever you create a new instance, it will be the same connection and execute query execute the query using the same connection. So since it there there can be possibility of only 1 instance, so in this application, there'll be only 1 connection.

This is, uh, fetch data. Fetch data cannot return the exception as we received it. Uh, it's a pure Python. So, basically, in the try catch, I can see response on JSON. So if it is a JSON response, it's returning just, uh, JSON. If it's anything else, it will it is going in exception. And, uh, if it is going in exception, we need to return some empty data, some error code or invalid, I should be handling that API error, basically. Uh, but if I'm returning Python exception again, It's going to it's not going to work. It's a bad way of doing it. Basically, here, We need to try. And if it is a exception, we need to have some proper formatting. Um, so, yeah, my Once this, uh, response code, I can check whether it's a 400, 500, whatever. Based on that, I need to take action, just not and return the exception. That doesn't make sense. At least I can return fetch data as false or something like that or an MDJson response. That might be more

Okay. Uh, basically, uh, we are deploying a uh, web application, which was developing in developing in Django. So first, We were using, like, normal EC 2, but later, like, it was giving lot of latency, and also we implemented more to, elastic means tag. Then, uh, we use CloudFront to CloudFront and rotate any static Content, we sorted from s 3. So we use AWS s 3 for, uh, serving static, so we can make it a public bucket and So static. So those part of the, um, like, request won't come to the actual c two server. After that, yeah, we can do a lot of those DDoS attacks prevention in, uh, that AWS cloud front. So it won't, uh, any unnecessary, uh, spam request won't affect our application performance. So after that, Now easy to, uh, we are doing all the like, we can improve lot of creating part, by using, like, a lot of debug methods. So, uh, don't use first, last, and Django. So it will hit the database. Like that, we can do a lot of things. Uh, alright. The DB queries very efficient. That will also improve the performance. And, like, uh, again, if there is a lot of load, we can definitely, like, you know, implement auto scaling So that it will scale up whenever the request is high.

Okay. Uh, into enhancing the performance as is, um, it will totally depend on the scenario. Performance, basically, we use, um, easy to and, uh, we will use mostly easy to insert the Elastic Winstock, not directly. So that will, uh, help the so few things like, If there is something I need to retrieve very, uh, often, then there's no need to hit it in the RDS. So I will use a disk cache So that, like, now I will get it quickly. No need to do any connection or anything. Uh, if it is, Like, only storage kind of thing, we can do it through r d s, like, very the data which I want to show. But if it is for a temporary purpose, and I just want to, you know, um, get it fast, but It's only for a few, um, few few minutes or something. I can definitely store it in release. Any event based also, I can store in release so that That will announce the performance. And as I mentioned earlier, like, static content, we can serve. No need to go for server. And