Pradeep Darjee

Could I help you understand more about your background by giving a break? Okay. My name is Pradeep Darji. I started my career as an Android developer in DigiSolution Private Limited. After nine to ten months, I switched to SCOR Technology by Inteveted. I joined SCORD as a PHP developer. The company had its own framework in core PHP, and I worked on more than 15 plus projects related to e-commerce, travel, real estate, healthcare, and HRMS. After four years, I switched to the Republic, India, where I joined as a senior web developer. I worked in Laravel and Bucchias over there as well. And after one year, I switched to Midtech Side Technology Private Limited. Metrexight Technology Private Limited is a product-based company. So, I worked only on a single product for four years, and the product was based on Laravel and VGS. I also handled two small teams over there. One team had one member, and another team had three members. Apart from this, my career experience, I have an MCA, Master of Computer Application, in 2013, and I pursued a 7.7 CGPA. I also did a bachelor's degree in BSc bioinformatics and pursued a 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 eager loading relationships, and I will optimize database queries. For that, optimizing database queries, I can use indexing first. I will apply indexing over the columns where needed, and I will select only those columns needed in the select statement. And I will use caching for data and indexing over columns used in joins. And yeah, I will use chunking as well to reduce time, so that will reduce the time.

It's a back-end process. You are working on the integration of user-facing elements developed by the front-end developer. How would you approach this integration to ensure consistency and performance? Integration of user-facing elements, yes. We're working on equalizing the integration of user-facing elements. Integration of user-facing elements is the moment. So, what I'll do is create a layout for the user-facing element developed by the front-end developer, like the header, footer, and body content of the page, and the navigation bar as well. We'll create a separate file for this, and I'll use the Laravel blade templating. I'll create separate files for all of this, and I'll create a master layout including all of these. For the dynamic content, I'll use sections in that, and I'll heal those sections in the master layout. That's how I will integrate this.

To optimize database schema and queries for a PHP application that frequently experiences load spikes, okay. So, to optimize database schema and queries, I'll talk about the database. There are two kinds of engines used for database schemas. The first is MyISAM, and the second is InnoDB. Generally, MyISAM is used for small projects, and it doesn't provide transaction and foreign key constraints, but it allows table-level logging. On the other hand, InnoDB is generally used for larger projects, and it provides transactions, foreign key constraints, and row-level locking. Okay? So, I would choose InnoDB for the database. To optimize queries, you can use indexing over the columns that are frequently used in joins. And, I will add only the selected columns in the select statement, which are needed. Third, I will use caching for the queries that are frequently used. Fourth, I will use chunking. I will divide the response into chunks, and Laravel will only provide chunking for that, which will optimize the query.

The method you would use to secure RESTful APIs endpoint in a Laravel application. To secure a Laravel application, you can use total middleware that will limit the number of requests or specific period of time. Like, you can set requests to 60 per minute. So you can use the throttle middleware there. And, you can use the latest Laravel auth middleware that won't allow your APIs to access without having access to it. So you can use that middleware. And, one more thing, I would use strong passwords for the credential API access. So that would be my approach, and I would use tokens as well. And I'll create encryption keys to strongly protect cookies, and I will implement a token-based authentication system for accessing 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, video. Video is used to connect the database, So that will in that will ensure SQL injection attacks, vulnerabilities, and, 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 it 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 it's not self or instance, self colon instance static error is equal to new database and returns cells. Yeah. There is a singleton design pattern being used. So, why singleton? Because the singleton design pattern will create an object of a class only once, and it will not create it for a second time. So, here we are making the database connection. So, we don't need to create a new database object of the database class again and again. So, here we put a condition for instance. If the instance is already created, then we will return it. Otherwise, we will create a new instance of the database class. So, it is a singleton design pattern.

Following called ESP code that uses an MDC framework concept identifies explain any potential problem with the way the database interaction is handled. Potential class user extends model, public function get user by email. Dollar email returns this TV. Yes, sir. This is the problem. Yeah. I think here you have to if it is in Laravel, you have to use Laravel's Eloquent and you can query for the user record using that email. So you can use db::table('user') and then using Eloquent's ORM. If you don't want to use Eloquent's ORM, you can use query builder as well, like db::query(). And in that, you can provide the or select statement. And also, you cannot select the star because it will return the password as well. So it will generally return the password in the select statement. We keep it hidden for the users. So that's the potential problem.

Describe how would you configure a Laravel queue system to hinder high volume of emails sending via postgreSQL transactional log. Yeah. To configure queue system, Laravel queue system, you can, execute command. Yeah. For that, you need to, 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, and the and listener for that as well. And, suppose there are, multiple task, and, 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, you can, provide your logic in the handle method, and you can dispatch that, job into the list listener. User successfully register event listener. you can dispatch that, job. And while creating job, you have to extend should queue, class. So it will keep on queue, and, it will execute, when it comes.

How can you leverage Laravel's polymorphic relationship to efficiently query polymorphic associations in a database? Okay, so what is polymorphic relationship? Polymorphic relationship is that one model can relate to multiple tables or multiple models. You can say that in Laravel. So, for that, you need to provide the relationship in one model, like user, address, and user post and command. So you can use polymorphic relationship, 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 hasMany and then model name. And, in the respective, it will show you will add relationship like belongsTo.

The factor that would influence the choice between using raw SQL and the query builder in a Laravel application for complex data manipulation would be performance. Raw SQL queries are generally faster than the query builder, especially when using lateral joins. So, that is the main thing, and that is the main factor. We will use raw SQL queries with the query builder.

That you have a PHP code base following the repository pattern. Okay. What step would you take to transition it into your dependency injection? You would start by identifying the dependencies in your code, which in this case are the repositories. So suppose you have a repository action, pattern. Suppose there is a user repository and there is a user controller. And you will pass that user repository in the user controller's constructor method. Laravel will automatically perform the dependency injection and automatically resolve the dependency. And after that, in any of the methods, you can use that repository class. So that's how Laravel will resolve the dependency and perform the dependency injection. For example, if you take an example of another thing that Laravel will already provide, if you see that in the controller method, there is a request, dollar request class, dollar request. Laravel will automatically resolve the dependency and perform the dependency injection over there. So you don't have to create any object of the class, and Laravel will handle those things.