
Technical Lead
Robosoft TechnologiesTechnical Architect
Everest TechnologiesTech Lead, Development & Support Web Application
Tech MahindraAssistant Manager, Trade Analysis & Fraud Detection
Tata Consultancy Services (TCS)Assistant Manager, Process Automation (Trade Settlement Process)
Tata Consultancy Services (TCS)Assistant Manager, Process Automation (Processing & Auditing of Financial Statements)
Tata Consultancy Services (TCS)Team Lead, Process Automation (Trade Settlement Process)
Tata Consultancy Services (TCS)Developer, Process Automation (Trade Settlement Process)
Tata Consultancy Services (TCS)
Git

AWS Cloud

Apache Kafka
.png)
Datadog
.png)
Docker
.png)
Jenkins

Splunk

Kubernetes

GitHub

Eclipse

Notepad++

PyCharm

Sublime Text

Visual Studio

Elastic Search

Apache

Kafka

Django
.png)
Flask
REST API

Elasticsearch

HTML

CSS

Bootstrap

Angular JS

MySQL

PostgreSQL

SQLite

AWS
Azure

Pandas

Power BI
Responsible for below activities:
Responsible for below activities:
Responsible for below activities:
Hello. So, basically, I have 14 years of experience into Python and Python rated frameworks. And then with the cloud technology, I have close to five years of experience. And I have worked on multiple projects with domains like banking, e-commerce, manufacturing, healthcare, and the media domain, which I worked on. The Python and Python rated frameworks like Django, REST APIs is something which I have worked in the last project, along with the AWS services close to 13 AWS services which I have used. And that's it from my end. Thank you.
Well, there are difference 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 will help you in making all the APIs like create, retrieve, update and delete, whereas the view actually helps you to create a single API one at a time. So that's the basic difference. And along with that, you like 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 helps you to quickly make all the code operations. And even you can customize that, you can customize that as well as per the requirement. And the view specifically gives you like something like a single API view, view for retrieve view is there, then for create, there is a create view, the 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 mostly most of the times, you may be in the requirement of making either read or update or create APIs. So in most of the cases, you may use model view set, which is a faster way of development. Thanks.
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 and which is done at the back end by the JWT and that will help you and if it's validated, authenticated, you get the response, a valid response from the API, otherwise 403 response you will get that is a forbidden response. Now coming to what you pass to the JWT thing, well, you need to pass to the APIs, any API initiating you will pass the bear token, bear token indirectly it's 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 which actually identifies authenticates the users, whether the user is a legitimate user or it's a user which is not having access to the API. So based on the if the it's a positive authentication, 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, thanks.
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, the foreign keys, foreign keys means a foreign relation within the table. And you may have one to one relationship or you may have one to many relationship with the table. When you have 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, a relation with one to many 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 any of these libraries and you can use it as per the response, the required response you need to send in that. Thanks.