Naresh Suresh Tanwade

Could you help me understand more about your background by giving a brief introduction of your side? Hi. Myself, Narish Tanavde. I living in Komooten, Ohio Mumbai. I have over 7 plus years of experience in PHP, MySQL, jQuery, JavaScript, AJAX. Also worked on Laravel Codeignator. Also, knowing, uh, GraphQL and working on, uh, Fintech, uh, projects. Uh, In our projects, uh, we show overall profit and loss of the client. You can request for a IPO. If IPO is allocated to that particular client, then, uh, it will be shown in the, uh, the, uh, current session of the equity. That's, uh, all, uh, that we show for it. And, uh, after that, uh, we I'll, uh, I can conclude that we show the overall performance of the client, uh, at what stop loss was he did, and that's it.

Describe a situation where you have to optimize database schemas and queries for PHP application that frequently experience a load spike. Sending, uh, the, uh, the data to the multiple clients, uh, where a problem. So we created an, uh, cron cron cron job. And using that cronjob, we can, uh, send in the background. So which can, uh, which can be sent successfully to all the clients, and, uh, user will get the response as soon as possible. Also, optimizing query, uh, whenever there is a lot of load on the database query database. So optimizing query by using indexes, uh, uh, which helps us to query, uh, the to the tables, uh, at the faster rate, uh, whereas, uh, uh, also writing triggers, uh, for which, uh, to indicate that particular action has been done. So, for example, after insert, before insert, after update, before update, after delete, before delete. So we can, uh, uh, track that, uh, activity has been done on that table. That's it.

What could be your strategy to avoid the SQL injections vulnerability in PHP activation using MySQL as, SQL injection, uh, vulnerability can be stopped by using, uh, prepare statements uh, while querying to the database, uh, so it will be easier uh, and, uh, no, uh, no vulnerability can happen, so, uh, from the outside. For example, if, uh, there is a login screen and there is a, uh, username and password, If we write a plain MySQL query, so we can, uh, uh, write anything means, uh, in, uh, username, we write name or anything one. So it will be always successful. So to stop this, uh, vulnerability, we can, uh, upload, uh, we can use, uh, prepare statements queries. So, uh, it will be checked for a particular parameter. If it is wrong, then, uh, it will be uh, redirect through the login page. That's it.

In scenario where you need to roll back the last 3 migrations in the Laravel, which command do you execute? 3 migrations can be, uh, can be rolled back by using a a migration, uh, path, uh, giving PSP artisan rollback and FN FN class, uh, equals to the path, uh, of the migration file. So it will be rolled back.

For the restful APIs in PHP, what could be an effective way to limit the rate of request coming from single user? We we can, uh, reshuffle. We can use a throttle in Laravel so which, uh, we can identify the request coming from a particular user, uh, we can read the also, we can read the number of requests per seconds or or a 5 minutes. So we can identify uh, what are, uh, and we can keep the API for particular request coming from a particular user. So we can identify it, and it will be helpful to limit the request, uh, coming from particular user.

How can you leverage, uh, Laravel elegant relationship to efficiently query polymorphic association in database. Uh, there are, uh, 4 types of relation, 1 to 1, 1 to many, many to 1, and many to many. So we can use that relationship for, uh, efficiently query the Polymercic, uh, Association. So, uh, belongs to we can, uh, write the write in model. Like, it belongs to, uh, belongs to function in the model. And, uh, we can, uh, write the same, uh, query for that. And, also, we can, uh, if, uh, has the many relation relationship, so we can, uh, have the has many function in the model, and, uh, we can, uh, write the particular, uh, query for that.

Below is a PHP function designed to create the restful API response, point out any issue with this function, and explain how it might violate the solid principle. E function create API response, data status, error. Response score status. We'll use a creation function designed to create a restful API. Point out any issue with this function and explain how it not an issue with this function and explain how it might violate the solid principle. As, uh, as I can see that the function is only created, uh, which shows the only the header HTTP response code, which use direct directly written before the the output has come from the API. So it will be distracting and echo the and return directly first. So it should be awarded, and HTTP response code should be directly received from the response file.

Review the following PHP code that uses the MVC Framework concept. Identify and explain any potential problem with the way the database integration is handled. Review the following PHP code that uses the MVC Framework concept. Identify and explain any potential problem with the way the database interaction is handled. class UserExtentsModel public function getUserByEmail returnedUser Review the following PHP code that uses the MVC Framework concept. Identify and explain any potential problem with the way the database integration is handled. class UserExtentsModel public function getUserByEmail returnedUser review the following PHP code that uses the MVC Framework concept. review the following PHP code that uses the MVC Framework concept. class UserExtentsModel public function getUserByEmail returnedUser

explain any complex migration you should use in the laravel to transfer single table inheritance design to multiple multi-table inheritance design if you are having a table of user in which we store multiple details of user so we can divide in the multiple parts if user is containing so we can create a table of user account in which we can store only the user account related fields like user user user user name email mobile is active or not whereas we can use the ID primary key in user details table user user account details we can say so in that we can store the user related means a bank account ID bank bank name IFSC so all the data can be stored also if one user is having a multiple hobbies so we can create the another table in which we can have a table we can map we can create the hobby tables and that will be listed the multiple hobbies whereas user hobbies can be mapped like a user ID and hobby ID so it will be mapped for example one user has a ID number one has a singing dancing playing cricket hobby so that in that table user hobby table we can see that table is holding user ID 1 1 1 and particular to that we can see the hobby IDs so we can this way we can migrate the single table into the multi-table inheritance design that's it

Which Laravel method you would would you utilize to ensure authenticity when updating multiple related models? Uh, using, uh, Lara will update her save save query, uh, as it will save the deleted one. Also, we can while updating any, we can, uh, on on update case care for, uh, means, uh, any foreign key relationship is there, uh, in our table. So any action done on on the base table will also reflect to the related table, uh, also. So we can, uh, mention the foreign key and on any changes in the action will be also taken on, uh, the particular tables.

What are the best practices in PHP for handling exception while maintaining the restful API, readability, and consideration. Best practices in PHP handling exception. Uh, exceptions can be handled while, uh, you maintain the restful APS, uh, and checking, uh, the we we should maintain the logs of where from where the request is coming. Uh, we can maintain the IP device. It is coming. It is not, uh, either to any script or that. So we can maintain the the source, uh, of request coming to the API. And, uh, uh, if, uh, unrelated sources there, we can block the, uh, the request, uh, from any Kron or particular IP. Also, we need to, uh, check, uh, check the, uh, to We we will also maintain the token related functionality. So whenever any user is using our API, so we can maintain the token, and we'll store it in the DB while uh, request is coming from any user. We'll, uh, have the username and password or token So we can, uh, uh, while coming request, we can check that, uh, token is matching to the user. And if it matches, then, uh, it will be given access to the API. Otherwise, it will be redirect, uh, to, uh, the source, and it will it will be, uh, uh, given, uh, error that, uh, you are not a authorized version to access the API. So in that way, we can add many, uh, handling handling exceptions. Uh, and we can, uh, successfully, uh, clear the restful APIs. And more about yeah. That's it.