Vishal Singh

Hello. So, I have 14 years of experience in Python and Python-rated frameworks. Additionally, with cloud technology, I have close to five years of experience. I have worked on multiple projects across various domains, including banking, e-commerce, manufacturing, healthcare, and the media domain. I've also worked with Python and Python-rated frameworks like Django and REST APIs, as well as AWS services, utilizing close to 13 different services. That's it from my end. Thank you.

Well, there are differences between a view and view set, and a model view set. Basically, it is a REST framework used for REST API endpoints. Model view set and view set actually help you in making all the APIs, such as create, retrieve, update, and delete, whereas the view actually helps you to create a single API at a time. So that's the basic difference. And along with that, you like to use the model view set or the view set, you use the router to define it, whereas for the views, you have to individually define it differently in the urls.py file. So the basic difference is the model view set and view set actually help you to quickly make all the code operations. And even you can customize that, you can customize it as well as per the requirement. And the view specifically gives you a single API view, such as a retrieve view, then a create view, and generic views are also there. So that way you just make a single API with respect to the code operation. Both are used as per the requirements. But when you have a mostly most of the time requirement of making either read or update or create APIs, so in most cases, you may use model view set, which is a faster way of development.

But JWT token is actually used for the authentication purpose for generating the token and you being the legitimate user of the API, you need to pass the token and then that token will be authenticated as per your credentials, which is done at the backend by the JWT. If it's validated and authenticated, you get a valid response from the API; otherwise, you will get a 403 response, which is a forbidden response. Now, coming to what you pass to the JWT thing, well, you need to pass to the API any API that initiates your request will pass a Bearer token, the Bearer token is indirectly an encoded one, if you decode it, you may find that some keyword is there which relates to your credentials. So, that using that, the JWT actually, the library, identifies and authenticates the users, whether the user is a legitimate user or not having access to the API. So, based on the authentication, if it's positive, then the API will provide you the response with 200, 201, or maybe it's deleted then 204, so according to that, as per the API, you will get the response, otherwise, it will return 403, forbidden.

Well, select related and prefetch related is something which is used in Django framework. Yes. And select related and prefetch related is something when you need to customize the response and you have in a table, foreign keys, which means a foreign relation within the table. And you may have one-to-one or one-to-many relationships with the table. When you have a one-to-one relationship with a table and you want to fetch the data of another table, then you can use select related. And in case you have a field with a one-to-many relationship within the table and you want to fetch the data of that table, you can use prefetch related. Once the data is fetched based on either of these, you can use it as per the response, to send the required response. Thanks.