Pradeep Darjee

Could I help you understand more about your background by giving a break? Okay. Uh, my name is Pradeep Darji. I started my career as an Android developer in DigiSolution Private Limited. After 9 to 10 months, I switched to SCOR Technology by Intevited. I joined SCORD as a, uh, PHP developer. Uh, Company was having their own framework in core PHP, and I worked over there more than 15 plus projects related to ecommerce, travel, real estate, health care, and HRMS. And after 4 year, I switched to the Republic, India where I joined as a senior web developer. I worked in Laravel and Buchias over there and as well. And after 1 year, I move I switched to the Scott, uh, Midtech Side Technology Private Limited. Metrexight Technology Private Limited is a product based company. So I worked, uh, only on single product for 4 years, and the product was based on Laravel and VGS. And, uh, I also handle 2 small team as well over there. Uh, one team with 1 member and another team with 3 member. That's it. Apart from this, my career experience, I have had MCA, master of computer application, uh, in 2013 and pursued 7.7 c g p a. And, uh, I also did bachelor degree in BSc bioinformatics and, uh, pursued 69% in my graduation.

What would be our approach to reduce API response time in a PHP serving a restful request? Okay. So my approach will be using caching and, uh, using I will use, uh, uh, eager eager loading relationship, and, uh, I will u I will optimize database, uh, queries. So for that for optimizing database query, I can I will use, uh, uh, indexing first? I will, uh, I will apply indexing over the column where wherever needed, and I will select only those those columns, whichever are whichever are needed in the select statement. And, uh, I will use caching for, uh, for data for for for the queries. I will use indexing over the column wherever, uh, which are used in there and, uh, join closed. And, yeah, uh, I will use chunk chunk as well and to reduce the times so that will reduce the time.

It's p back end. You are working on request integration of user facing element developed by front end developer. What how would you approach this integration to ensure consistency and performance? Integration of user facing element. Yes. We back in you are working on equalize integration of user. Integration of user facing the moment. Okay. So, uh, what I what I'll do, uh, I will create a layout for that user user facing event developed by front end, uh, like header, uh, footer, and body content of the page and the and the navigation bar as well. And we'll create the separate file for this, and, uh, I will use, uh, if I talk about the Laravel, I will use blade templating. I will create separate file for all of this, and will create a master layout, uh, including all of these. And, uh, we'll for the dynamic content, I will use section in that, and I will heal that section in the master layout. So that will that's how I will integrate, uh, integrate this.

Situation where you would have to optimize database schema and queries for PHP application that frequently experience says load spike. Okay. So to optimize database schema and queries, uh, so so first, I'll talk about the database. There are 2 kind of engine are being used here for database schemas. For 1st is, and 2nd is, you know, d b. Generally, is used for small, uh, kind of project, and MISM provide doesn't provide transaction and, uh, foreign key constraint, and, uh, it allows table level logging. And while, you know, DB is generally used for, uh, larger larger size of project, and it provide transaction, uh, foreign key constraint and row level locking locking. Okay? So I will, uh, I will choose InnoDB for the database And, uh, to optimize queries, uh, you can, uh, you can use indexing over the column wherever needed and those where which whichever column are being frequently used in there and join close. And, uh, I will and second thing is that I will you I will add only, uh, selected columns in the select statement, whichever are needed. Uh, third thing, I will use caching for the queries, uh, where the frequent the whichever the queries are frequently being used used. 4th thing, I will use chunk. Uh, I will divide that, uh, response in the chunk and will use chunk. Laravel will only provide chunk for that, so it will optimize the query. And, uh, Yeah. That's it.

The method you would use to secure RESTful APIs endpoint in a Laravel application. Okay. To secure to secure Laravel application, you can you can use total middleware, uh, that will limit, uh, number of requests or specific period of time. Like, you can request on, uh, 60 requests per minute. So you can use throttle middle there. And, uh, you can, uh, in latest Laravel, you can use auth auth, uh, auth center, uh, middleware that that won't allow your APIs to access without having, uh, act without having without having access to it. Okay? So you can use the, uh, middleware. And And, uh, one more thing, I will use strong password for the credential, uh, API access. So that would be my approach, and I will use token as well. And I'll I'll create encryption keys keys for strongly protect cookies, and I will implement token based authentication authentication system for to access the APIs.

What would be your strategy to avoid SQL injection 1 19 PHP using MySQL as the database? Okay. So to avoid SQL injection, I will use video. Video or, uh, uh, video. Video is used to connect the database, So that that will in that will ensure SQL injection attacks, uh, vulnerabilities, and, uh, it it will not allow SQL injection for that.

This BSP code snippet that involves a common design pattern. Okay. Can you identify which design pattern is is using and explain the purpose of each class in the pattern? Database private static instance This is equal to null. Property, static property instances, private function constructor, public static function, get instance. If is not self or instance, self colon colon instance static error is equal to new database and returns cells. Yeah. Uh, there is a a singleton design pattern is being you is used. So, uh, why singleton? Because singleton design paper, uh, will design pattern singleton design pattern will will create, uh, object of class only once, and you it will not create for a second time. So that, uh, here we are making the database connection. So, uh, we don't need to create a new database, uh, objective new database class again and again. So here we what we did that, uh, we put a condition for instance. If instance is already created, then we will return it. Otherwise, we will create new instance of database class. So it is a singleton design pattern.

Following called ESP code that use an MDC framework concept identify explain any potential problem with the way the database interaction is handled. Potential class user extend model, public function, get user by email. Dollar email return this TV. Yes, sir. Sir. This t p. Yeah. Uh, here, uh, I think here you you have to if it is in Laravel, you have to use, uh, Laravel eloquent Eloquent, and you can you can query for the, uh, user record using that email. So you have you can use, uh, uh, db colon db colon colon user. And, uh, and then using you can use, uh, Eloquent ORM. If you don't want to use Eloquent ORM, so you can use query builder as well, uh, like d DB colon colon colon query, uh, function. And in that, you can provide the or select statement. And, also, you you you cannot select the star because it will return password as well. So it will it it will, uh, generally, we don't, uh, ex don't return password in the select statement. We keep it hidden for the users. So that is the prob potential problem.

Describe how would you configure a Laravel queue system to hinder hinder high volume of emails sending via postgreSQL transactional log. Yeah. To to configure queue system, Laravel queue system, you can, uh, execute command. Yeah. For that, you need to, uh, like, if I take an example of user registration, after successful user registration, you need to send some email to user. So for that, you need to create an event, uh, and the and listener for that as well. And, uh, suppose there are, uh, multiple task, uh, and, uh, it is taking longer time to send an email, so I will create a job for that as well that will keep on queue. So I will create a queue for that using Laravel, and you can create a job using PHP addition make colon job and your class name. And, uh, you can, uh, provide your logic in the handle method, and you can dispatch that, uh, job into the list listener. User successfully register event listener. Uh, you can dispatch that, uh, job. And while creating job, you have to extend should queue, uh, class. So it will keep on queue, and, uh, it will execute, uh, when it comes.

How can you leverage Laravel elephant relationship to efficiently query polymorphic association in a database? Okay. So what is polymorphic relationship? Polymorphic relationship is that, uh, you can relay relate, uh, one one model with multiple table or multiple model. You can say that in Laravel. So, uh, for that, you you need to provide the relationship in one model, uh, like user, address, and, uh, user post and command. So you can you can use in the comment, you can use polymorphic relationship, uh, like, comment is related to user and comment is related to post as well. So you can in the post in command model, you will use you will create a polymorphic relation like has polymorphic and then model name. And, uh, in respective, it it will show it will we will add relationship like belongs to.

What factor would inter influence the choice between using and raw SQL array in a Laravel application for complex data manipulation. What factors would influence the choice between using Yeah. So factor would be that lateral Eloquium to RM is slow, generally slow rather while query builder, raw SQL queries is faster than the Eloquium to RM. So that is the main thing, and, uh, that is the main factor. So, uh, we will use, uh, SQL queries using query builder. So that will run faster than the.

That you have a PHP code base following the repository pattern. Okay. Uh, what step would you take to transition it into your dependency injection? It using. Okay. So suppose I have a repository action, uh, pattern. So what if there is a, uh, suppose there is a user, uh, repository and and there is a user controller. Okay? And, uh, so, uh, I will I will pass that user repository in the user con constructor method of the user controller. So Laravel will automatically perform the dependency injections, uh, and automatically resolve the dependency. So and, uh, and after the in any of the method, you can use, uh, that uh, you can you can use, uh, in any of the method of the user controller, you can use the method of, uh, that repository class. So that's how Laravel will resolve the dependency and perform the dependency injection. So, like, for example, if I take an example of another things that, uh, Lara will already, uh, provide, If you see that in controller method, uh, there is a request, dollar request, request class, dollar request. So Laravel will automatically resolve the dependency and perform the dependency injection over there. So do you didn't have to create any object of the class, and Laravel, though those thing will be handled by the Laravel. You can yeah. That's it.