I have 15 years of overall experience in software development, with 6 years of expertise in Python, Django, REST APIs, MySQL, PostgreSQL, SQL Server, and ERP. I have also worked on cloud technology i.e. AWS, specifically EC2, S3, Lambda, API Gateway and RDS. I have developed, and maintained web based ERP and web applications and services using these technologies, following best practices and standards. I have also experience with REST APIs and databases, to automate and streamline business processes and data flows, also having experience in data modeling, query optimization, team handling. I am passionate about learning new technologies and solving problems.
Technology Analyst
Bounteous X AccoliteSenior Technical Lead
Servion Global Private LtdSr. Python Developer
Servion Global SolutionsSenior Python Developer
DevopsInternationalSenior Technical Lead
Servion Global Private Ltd-IndiaSenior Technical Lead
Servion Global Private Ltd-IndiaSenior Python Developer
DevopsInternational-IndiaDjango (python)/SQL Developer
Office VcanDjango (python)/SQL Developer
Office Vcan-IndiaSenior Python Developer
DevopsInternational-IndiaSr. Engineer (Developer cum EDP/ERP In-charge)
SEE Linkages Privated LimitedERP Consultant
MobileERP Pvt LtdDjango (python)/SQL Developer
Office Vcan-IndiaERP Consultant
MobileERP Pvt LtdSr. Engineer (Developer cum EDP/ERP In-charge)
SEE Linkages Privated LimitedPostman
Angular
React JS
Django ORM
Apache Airflow
GraphQL
Stripe
WordPress
Shopify
Insomnia
Celery
Shopify
Django Rest Framework
Stripe
AWS Lambda
AWS API Gateway
Shopify
Creating backed logic using Python-Django and Django Rest Framework library.
Generating API which can be consumed by Angular application.
Work Flow management using Apache Airflow.
Used Django ORM for querying database to perform CRUD operation.
API Testing using Postman. Python Django
My son locked eyes. And, I completed 15 years in the IT industry. Started my career in 2018. To 18, and, working ceiling is fairly limited as a developer. What I've worked for almost 10 years. And after I joined DevOps Internet, office weekend, in 2018. What they have worked for 2 years and, worked 3 projects ERP Management System, ERP, then school management system, and and, agriculture management system. Over there. Technical stack use of Python Django as framework and MySQL. A new database. In 2022, I moved to DevOps International and worked in 2020, I, moved to Work International, and but for almost 10 years, 2 years, and, technical stack use of Python, Django, rest framework. I involve the project. It was GraphQL also. And, 2022, I switched to Sovereign Global Social Private Limited. For there, I worked this is my current company. So it's almost 2 years from for now. And, Atlas type of, ER, it we are using this Python Django Django dash framework, Celery, and for a cloud man cloud, we are deploying our system or application to AWS. Yeah.
So JWT is, JSON Web Tokens. So why we use this because it is a h 22 to 6. 1, Okay. And, we use it for, encryption of our information. Also, we use that for token generation. Actually, it's a token which we use for author authenticating, User. So whenever we use a token or whenever we pass the token in the request site request to a server, then that token will have the information about the user credentials and which can be authenticate it against our against the particular user in the database, but we have stored. And, also, it is not like that only can store username and password we can have. Number of information in the token. We can pass that out. And the front end team or any of that the client could retrieve those details from the token itself. And, it is, beneficial of our simple token is because simple token could be, it could be decoded, and you don't have other any any other information except the Also, in JWT, we have a access token, and we have a refreshed token. So, whenever the access token has a less time, what to say, that it expire expire time is less than the refresh token. So when the Access token get expired. We have to generate a new token using the refresh token.
View is not function which we can use to write our business logic. After, it is mapped to the URLs.py or and, where we give that function name in the URL.pyway. And, view set is a class base of view, so we have created a class and, we can map that class in the URL dot p y. 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 exact of there's a, set of rules like our consent contract like, create a create, update, delete, and get So you can use all those methods. And, it also in the view sets and model view sets in view set, we have a URL dot UI. But with models dot p y, models, view set, we to use this router So it could be a simple router and it could be master routers. And if you want to add any other end point, then we can use the record action method to create a endpoint within the class itself. There is model using 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 user class. And write the function for that. So you can just have to write only single class and all the endpoints will be defined within that. And you don't have to create the rejects of the URLs. The router will take care of all those things.
So select related is, to be 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 a employee table and sorry, company table. And I have a country as a foreign key, so I would have a country model in separate application or a as a separate class. Then if I want to fetch the country details along with the sorry, company details along with the country, Details. Then I can use the select related and, in the company models, like, company ORM query, I will call select late dot select later. 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 I'm method to fetch details or data from the database. Until unless you don't fetch the date don't use the data, it will not be fetched from the database. So if you don't use the selected and you have just given the company dot objects at 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 in it will be a join, you know, join query if I 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 a inner join of company and country when we are using select related And when you have a many to many fields, like, if you have a com company table, you have a department table, or you can say if there is a employee table and department table. So 1 employee could be related to 2, main department and one department could have a many employees. So it it is, like, many to many relationships. So if you want to fetch employee with all the deep departments, then you can use the prefetch related. In database, I will use I will say that it is a in line query or a inquiry where you have to fetch all those, details of the corresponding table, like, on many to many table, like, if you are employee and, like, then I want to fetch all the table all the details for employee and the department.