Akash khatri

My son locked eyes. And, I have completed 15 years in the IT industry. I started my career in 2018. The ceiling for growth as a developer is fairly limited up to that point. What I've worked for almost 10 years. After I joined DevOps Internet in 2018, I worked there for 2 years, and during that time, I worked on 3 projects: the ERP Management System, the school management system, and the agriculture management system. Over there, the technical stack included Python, Django as a framework, and MySQL as the database. In 2022, I moved to DevOps International and worked there until 2020, then I moved to Work International, but for almost 10 years, I worked with a technical stack that included Python, Django, and the rest framework. I was involved in a project that also used GraphQL. In 2022, I switched to Sovereign Global Social Private Limited. That's my current company, and I've been working there for almost 2 years. We are using a type of diagram, specifically Atlas, and our technical stack includes Python, Django dash framework, Celery, and for cloud deployment, we are using AWS.

So JWT is JSON Web Tokens. Why do we use this because it's a huge advantage from 22 to 6. Okay. And, we use it for the encryption of our information. Also, we use it for token generation. Actually, it's a token which we use for user authentication. So whenever we use a token or whenever we pass the token in the request to a server, then that token will have the information about the user credentials, and which can be authenticated against the particular user in the database, that we have stored. And, also, it is not just that only username and password we can store in the token; we can have a number of information in the token. We can pass that out. And the front-end team or any of the client could retrieve those details from the token itself. And, it is beneficial because our simple token is because a simple token could be decoded, and you don't have any other information except the one that you've stored. In JWT, we have an access token, and we have a refresh token. So, whenever the access token has a shorter time, I mean, its expire time is less than the refresh token. So, when the access token expires, we have to generate a new token using the refresh token.

View is not a function which we can use to write our business logic. After that, it is mapped to URLs.py where we give that function name in the URL.py way. And, view set is a class-based view, so we have created a class and we can map that class in the URL.py. And see, in the class, we can write our current operation. And that current operation can be called using the endpoints. And model view set is the same as this view set where we are writing our business logic in the class-based form. And when we are using this model, we said we have a set of rules like our consent contract, like create, update, delete, and get. So you can use all those methods. And it's also in the view sets and model view sets that in view set, we have a URL dot UI. But with models.py, model view set, we use this router. So it could be a simple router and it could be a master router. And if you want to add any other endpoint, then we can use the router's action method to create an endpoint within the class itself. There is model using a class itself. So you can have, like, get token or get employee or any of the extra URLs you can directly write into the class model view class. And write the function for that. So you can just have to write only one class and all the endpoints will be defined within that. And you don't have to create the routes of the URLs. The router will take care of all those things.

So you select related is used when we have a foreign key in a model. And we want to fetch that table along with the foreign key or foreign key foreign key tables. Like, if I have an employee table and a company table. And I have a country as a foreign key, so I would have a country model in a separate application or as a separate class. Then if I want to fetch the country details along with the company details along with the country details. Then I can use the select related and, in the company model's ORM query, I will call select_related dot select_related. And include that country model so it will be like a single query. Which will fetch the company details along with the country details also. It will not be like that. When you start up because Django has a lazy loading method to fetch details or data from the database. Until unless you don't fetch the data, it will not be fetched from the database. So if you don't use select_related and you have just given the company dot objects, all and you want to fetch the country, then there will be a separate query for that. So in terms of database, it will be a join, you know, join query if I'm using select_related. Else, it will be a normal query, and then, there will be a separate query for fetching the country. So in database terms, I will say, it is an inner join of company and country when we are using select_related. And when you have a many-to-many field, like, if you have a company table, you have a department table, or you can say if there is an employee table and a department table. So one employee could be related to two main departments and one department could have many employees. So it is, like, many-to-many relationships. So if you want to fetch an employee with all the deep departments, then you can use the prefetch_related. In database, I will use I will say that it is an inline query or an inquiry where you have to fetch all those details of the corresponding table, like, on many-to-many table, like, if you are an employee and, then I want to fetch all the details for employee and the department.