Shraddha Jilkar

Hi. Um, myself, Shanda Jilka. I have worked for 7 years, and I have been mostly working as a first time marketing developer. I have worked for documentation creation on the projects, the slides that are on the projects, SDLC on the projects. Then I worked on timeline management modules management from shared and Azure task management. And the manager kind of team with the size of core members. I have worked on the ping pence service APIs and a full time back end maintenance on the projects. Using PHP MySQL, keep PHP coordinator, JK range JavaScript. Thank you.

One Laravel feature facilitates the easy management and testing of HTTP restock to restful APIs. What Laravel feature passing date? The the key c management and testing of HTTP request to rest APIs. This features allow you to define and organize various API endpoints, making it easier to interact with them during development and testing phase. By using ports, you can capture the API related logics, such as requesting formatting and response handling into a dedicated.

Describe a situation where you would have to optimize database, schemas, and queries for a PHP application that frequently experiences loads, spikes. Then we have to, uh, identify the bottlenecks, bringing by analyzing the database schema as a query performance using profile tools like database query logs. Then while optimizing the schema designs, reviewing the database schema to ensure it is properly normalized and indexed query optimization, uh, by adding the appropriate indexes and reducing the number of database calls, implementing caching to reduce the load on the database utilized tools like and mem catch. Horizontal scaling in the database server is struggling to handle the load. Consider scaling horizontally, adding 8 load balancing, implement load balancing to distribute income to incoming traffic evenly across multiple databases. Monitoring and alerting set up the monitoring tools to continuously monitor the database. Regular performance, training, database optimization is an ongoing process regularly review and find the database.

As a team lead, how would you guide your team in transitioning a monolithic Laravel application to a microservices architecture? Uh, educate the training session. Start by educating the team about the Microsoft architecture. Everyone understands the principle behind the Microsoft architecture. Then access to the conducted throughout assessment for the existing monolithically and reliable application. Business domain define clear boundaries between different business domains and this application become post monolith. Breakdown the more application to smaller, more management service based on design and design and implementation regarding the design API issues appropriate communication protocols can tenderize services like Docker to ensure consistency and portability to the environment driven This current load balancing that under service is currently mechanical to enable the Microsoft is covered in community features, troubleshooting, monitoring and log logging solutions to track the performances and our ability and help on the microservice. The security concentration address the security concerns such as authentication, authorization, data protection, and both the microservices and the API gateway.

Mention a strategy to implement post grid as per partitioning for large data setting a PHP back end. We can do by we can do implement the post with the larger dataset by detecting the partitioning key, determining the columns on on which the partition dataset and this is. Engine strategy can implement the post grid partition for live datasets in a PHP back end. And do a strategy to implement post Versus Square partitioning for large dataset in PHP back end. By, uh, by choosing the right database by designing the database, the mass, implementing fast usage, logic, optimizing the query performance, handling the terminal maintenance monitor, and, uh, tune the performance, ensure the security

What would be your strategy to avoid SQL injection while while PHP application using MySQL as a database. Use the prepared statement. Uh, use the validate and sanitizing. Put avoid dynamic escape in special character. Then limit the database permissions to update PHP and MySQL version. Implement web application firewall. Educate the developers. Use the ORM libraries.

Examine this page before snippet that involve a common design pattern. Can you identify with design pattern using explain the purpose of each class in the pattern? Class database, private static instance for to null, private function construct, public static function get instant. It's self instant then self instant equal to new dataverse. Otherwise, return self instant. It may be, uh, it may be implementing the singleton design pattern. This part represent the singleton itself. It is a private static variable name instance, which hold the single instance of the database class. The constructor method is a private to prevent, uh, even the instant of the class from outside the get from the outside. The get instance method is a static method used to retrieve the single instance of the data in this class. Purpose of the each class is the single instrument design potential that the classes on the one instance have provided global point of access to the to that instance. In this scenario, the database class ensures that only 1 instance on the database connection is created throughout the application life cycle. This pattern is useful for managing resources that should be shared across multiple parts of the application.

Review the following page report that uses a MVC framework concept, identify, and explain any potential problem in the way the database interaction is handled. Class user extend model. Public function get user by email. Argument as a email. Inside the function, return dollar this at arrow d b arrow query. Select star from user when you may request to email. Close the brackets. In this, uh, in this function, in this function, we are, uh, using the we are using the class as a user, which, uh, we are taking the value of the email ID and checking into the database with from the user table where the email doesn't exist or not returning the same.

How you would configure a Laravel crease system to handle high volumes of emails sending via post screen and SQL cell transaction log. Set up the Laravel, uh, me system. First ensure that you have Laravel installed and set up. Then choose the 3, um, 2 data driver. You want to leverage host to transaction log. You can use a data disk queue driver. Configure data disk connection. Sure. The application is configured the database, uh, to create the connect cable, configure the reconnection. We can actually call the database, create the email sending jobs. Despite the email sending your postpaid job's done. Also, supervisor in the process manage to manage your work processing production to ensure the continuous processing.

What would be your approach to reduce the API response time in a PHP application serving this quick way request. We can create a catchy translation, like, a catchy classic phrases of sentences to avoid application translation. By translation of translating each page individually, batch multiple phrases together and send them in a single translation. In the past transitional API, choose a transitional API. It is optimized for the speed. Optimize API request Pre translate common phrases. Pre translate commonly used phrases of static communication translation. Utilize the content driver network to cache the transcript, cut it closer to end we use, uh, optimize the application code review and optimize the page for response by handling the translation request.

If you need to speed up a Laravel application, what strategies would you consider for optimizing query results? Uh, we can use data query caching. I will provide both inking in support for the query caching, and you can capture the results of the database queries using the other queries. We can use the eager loading. Use the eager loading to reduce reduce the number of database queries generated when retrieving related models. Query optimization review and optimize database queries to ensure they are efficient and use appropriate indexes. Use Laravel's query log current pi should low for inefficient queries. Database indexes, analyze the database schema and usage patterns to determine which column should be indexed for partial data caching, data caching, fragment access data, complex query result to reduce the need for a repeated database queries.

One of the best practices in PHP, filing the exceptions while maintaining a useful API readability and consistency. I use that in it should be stay status code, like, 200 for those successful request, 400 for the valid responder, 1 for the unauthorized request. Standardized error respond defines, uh, tuning identifier for the error, um, human readable message describing the error through custom exception defining custom exception classes for different types of errors that may occur in your application. Log exceptions and documents and error responses.