Tarangini p

So myself, Tarangini, I'm also having 12 years of experience in IT. I worked with different frameworks and technologies like PHP, Python, and Django frameworks, as well as REST APIs and more. So I'm into completely web development, with good exposure to API development and databases, such as mySQL. I have the ability to work both individually and as a team player. I've had experience as a team lead, as well as with project tracking, project status, and requirement gathering, including conversations with stakeholders. So I'm good to start my career.

We can go for a selective retrieval. We will use it whenever we just want to retrieve the data, and that can be worked with civilizations and passed as a response. We prefer the related data, and we can use that when we want to have some other operations done on the data given. So, that time, we can go for prefetching related data from the preloaded related ones. We will be processing our operations on the queries from the query result to the set, and that would be selected later and passed to the response.

So, views, we use it and models use it. Views, we can use when we want to render HTML as an output for the API. And use it whether it is going to be a normal JSON response or the kind of thing we can use for view sets. So for standard REST APIs, that would be good to go with view sets as we will be only getting the database details and sending the formatted response to the REST API. And model view set, where we'll be handling all the model data without getting any queries, like model data only alone, we will be sending that time we can go for model view set. For standard, standardized APIs, if you set the best option, that's what we can go with.

JSON Web Token, the first form, JWT works. JSON Web Token, we will be using, to authenticate two parties, like client and server. And, moreover, we use simple token authentication as well, where we will be exchanging the authentication token between a client and a server. So, what is JWT exactly? Since it's like JSON Web Token that would be exchanged. And, we have it was and most of the time, we have used a simple authentication token only, with the Authorization header, we've been sending it. So, it's not like I didn't get worked with that earlier. But as we are exchanging with the JSON format, I indicate that means that the exchange would be easier, I believe. And the reliability, as well, at the same time.