Ashish Gupta

Could you help me understand more about your background by giving deep introduction of yourself? With your respect to the sir, uh, thanks for this opportunity. My name is Ashish Soguptha. Probably, I'm representing the heartland of India, river district, which is post backbone within the majestic state of the. Professionally, I've been over 10 year of experience in software development with, uh, a focus of the 8 years in the merchant trade of ecommerce. Professionally, I've been over in this to on the hands on the various, uh, diverse project. And, probably, I'm hunting on the AWS Commerce Cloud, Inspire Edition, and Open Source. Uh, my expertise of, uh, custom module development, uh, team development, or any, uh, speed optimization, uh, data migration from 1,000,000 to 1,000,000 to 2. Uh, have our expertise, just like copy. We need to, uh, create or override, extend the functionality of a third party extension, uh, third party configuration on installation and number application. Any type of customization in the front end, back end, uh, we have a computer like that. And, uh, we have a most of the thing we have using the REST API for the, uh, creating the connect with the Salesforce opportunity. And third API for the ERP system by using these are the challenging task we have completed and these are the challenging tasks we have completed in my career about my academics and the commensurate of, uh, secondary school on both. Uh, did he recently completed 10th 12th grade with the, uh, uh, 1st division? This laid the groundwork of a subsequent in the field of computer science with the, uh, at Rajiv Gandhi, Peddi, Bhopal. Uh, my expertise on the various platform and tools encompassing on the Magento 2, Magento 1, PHP, HTML, JavaScript, jQuery, CSS, Angular, Jira, Bitbucket, REST API, GraphQL, and Jira Bitbucket to AWS Commerce Cloud. And apart from that, uh, I am extremely dedicated and honest person. Uh, in my leisure time, I'm, uh, find out the solace on the listen music and, uh, playing cricket match. Thanks for considering my application. Uh, thank you. Thank you very much. About, uh, my, uh, roles and responsibility, uh, so we have, uh, my roles and responsibility have partaking to the, uh, provide the guidelines, software technical guidelines, and, uh, monitoring the project deadline, making with the monitoring and, uh, overseas on the product development. So, uh, code review. And, uh, that is a a provide the including architecture collaborate, the teams, and another team member if it is required that uh, my specialties, the REST API working with that, um, and getting for the 3rd API. We have a directly discussed with the client about that, uh, regarding to the requirement by using team chat. Then we have a, uh, taking for the writing the, uh, developing right before, developing the, uh, tickets. Then we have a going to that, uh, for the, uh, testing that, uh, in boosting our engineers in invite, uh, integration server. Uh, then we have we're going to that, uh, testing that assigned to the QA. We will approve that, then we have a going to the, uh, uh, uploading the staging server. And then so, uh, we have a swing the demo with the client after, uh, each and every take, uh, finalize. We have a going to the

So, uh, rollback is still using the Magento deployment. So, uh, our development, that means we have using the breakpoint. Uh, we have added the console log. Uh, we have added for the console log creating the, uh, gen framework 3. Uh, they are about we have introduced for the gate method, post method. We have introduces the classes of the, uh, gen for for the regarding the. Uh, so they are about breakpoint we we introduced for that deployment process. That's been so for the this is a deployment process is a that's just, um, deployment so that mitigate the risk of a new bug introduced as we we use that, uh, just like we use the CICD pipeline, uh, using the process, uh, parallel steady strategy. And that's, uh, we will use the connect characterization concept. We have a use for the CICD pipeline strategy. Uh, we will, uh, implement the monitoring for the each and every time for the monitoring. And that's, uh, strategic patterns. We will use that, uh, that's we have to implement that, uh, that break point to the using, uh, break, uh, functionality roll back. Uh, there, we have a create data. And, uh, monitoring when we have a monitoring in the, uh, each and every time, uh, during to that, so we will uh, risk our strategies to the introduce of the new bugs just like up events. So we have a going to the implement that and monitoring that. So suddenly, what bug is coming, then we have a going to take the action as a, uh, same time without, uh, uh, lap lack on the time, and we will, uh, to into the action and take the action and complete the, uh, tickets. So, uh, Vax, uh, so these are the basic features of, uh, introducing in there. So, uh, uh, they are we have are using for that. And, uh, we have used for that, gate to, um, a Sonar cloud, uh, Sonar cloud, uh, that is a, um, very, um, best one. We will use the, uh, PHP, uh, CS, uh, PHP, CS, uh, application for that, uh, bugging the debugging the code, roll back that's there have a multiple statements we have are doing to that, uh, debugging the code for the new bug, introduce that. So, uh, we have used, uh, so suppose in that, we have used the PSPCS. So, uh, there so it will be, uh, testing for our module, uh, uh, modules, so everyone functionality component and write the unit testing, uh, what is the positive unit test and write unit test, negative unit test. Uh, then after where, uh, that if we are going to that talking about data, it is a check the functionality, um, uh, automation testing. Uh, so these things have a point to be include, then we have a going to the creator rollback strategies for the Magento development as a immediate risk of a new bug introduced.

So, uh, there have a, uh, many number of step, uh, to resolve the confliction, uh, between 2 Magento, uh, accents and affecting JavaScript functionality. Functionality. So we need to, uh, check that where is exactly, uh, JavaScript functionality, have a, uh, getting data. Uh, suppose that, uh, in some time, have a, uh, fetching the, uh, of the, uh, same suppose that we have, uh, implemented the 2 or 3, uh, 3rd party, uh, JavaScript jQuery, uh, and our extension for the, uh, uh, in the header. So that, uh, and, uh, that's this already have a happening in there. So confection will will occur. So simply, we will, uh, uh, check that scenario, uh, and, uh, that is a we will go into that. So, uh, find out the work, actually, where is a confliction occurring, uh, during to the, uh, application. Uh, then if it is, uh, uh, regarding to the library, which one is a third party library we are using, so we are getting the issue. Then, uh, simply we will, uh, try to the put the some JavaScript libraries or some JavaScript, uh, 3rd party URL in header and, uh, uh, which one is getting confection, then we have a, uh, we have a put in the, uh, footer. So by using this order, we will, uh, solve the, um, solve the problem. Uh, if we have a getting that's, uh, extension, so we'll we will use for the, uh, module dependency concept in there. So module dependency, that means it will be dependent on the your modules. Uh, uh, there have a 2 type of that's been several, uh, 2 type of a, uh, module dependencies uh, providing the Magento 2 hard dependency and, uh, soft dependency. So hard dependency, that means cities are getting the confliction on that is dependent on the 1, uh, uh, one module to the another one of the functionality completing that. So that's we have not going to the hard hard dependency. We will implement once, uh, Magento extension by using soft dependency concept of a module development. Uh, so in there, when we have implemented, uh, any things just like our our functionality, then, uh, we will use for their soft dependency concept. That is dependent on the one, uh, extension to another one, uh, extension. Uh, so if it is not getting any and they are up between the 2 module, uh, then, uh, 2 functions, uh, 2, uh, functions, uh, then easily we will, uh, going to identify that, uh, first one where we are getting exactly problem. Uh, we will identify that, uh, the, uh, page or a URL or code. Then we have a going to that, uh, put in the, um, disable the module if it is not required. If it is required, then we have a put that module for the space speaker, uh, block or the places by using the layout dot XML file for the 3rd party JavaScript URL. Uh, the score, we will need to implement that. We have applied for the footer. That means different different places, we will implement that and, uh, check that if it is working perfectly. So that's when we will resolve our, uh, confection in there. Then we have a going to the mini file that, uh, our JS CSS file. So these are the step, uh, by using there, we will, uh, resolve our conflicts and enduring the uh, getting confection on the Magento extension, uh, hard team functionality of the JavaScript.

How would you handle a Magento site update without causing downtime to live stream live system? So, basically, if we need to go on the, um, Magento upgrade, so, uh, first, I will in the live site without going to the downtime. Uh, so we will my first step is, uh, we will deep take the backup on the all folders and files. Once we have a get it completed on the all folders and so database backup, then we have a going to the, uh, copy of the create the copy of your composer dot JSON as a dot backup file. Uh, then after that, so we will check that our compatibility, what is the read harbor requirements for the just like a pay. If we are going to the upgrade for the 2.4.222.4.6, so there have a loss of a, uh, have a change just like copy composer have introduced that. GraphQL have introduced, uh, that much better security. And, uh, if we are talking about the, uh, PSP version, so 8.1. Jane framework have I introduced for the 3. Uh, REST API and GraphQL have a functionality, have enhanced that. Uh, security purpose have enhanced that. So, there have a, uh, lots of elastic as well by enhanced that hard, uh, 7. Uh, we have introduced that. So there, however, we need to check before, uh, we need to, uh, upgrade the these all applications. So supported application, uh, just like PHP, composer, uh, Elasticsearch, uh, radius cache, Vernice, but what we have installed there, then we have a upgrade that or the, uh, system. Then after that, uh, we have a going to the, uh, uh, run the our composer command, uh, composer commands. After that, we have a upgrade the all the system, then we need to go update, uh, update the our composer, uh, by using the now about the upgrade our, uh, by using command line in there, we will upgrade data. And, uh, without down downtime, uh, because that, uh, we have we're taking several time for their, uh, uh, some time because, uh, we have upgraded already, uh, each and everything. So in there, uh, and, uh, because that is we have taken the database backup file folder backup, So that's not a worry about that upgrade. We have a without going to the downtime, we will go into the run the upgrade command in there. And, uh, so, suddenly, once completed that, uh, we will check that functionality and, uh, each and everything working in the front end as well as of the back end, uh, order. We will try to the place the order from, uh, from home to be have a going to the, uh, order successfully in, uh, checking them email is triggering or not triggering. Uh, and if you, uh, check that each and every functionality should working perfectly, so that means these are the process we have a using for their then, uh, check that, uh, uh, that means we have a follow that some commands etcetera. Uh, some step in there, commands for the middle and 2 basic commands, run that, and then check the functionality on the front end, back end, and main section. Uh, each and everything working perfectly. So that means we have successfully, uh, completed our, uh, Merchanto upgrade from 2.4.2 to 2.4.6 successfully.

So in this, uh, in this cases, uh, we need to, uh, automatically, we need to update our Magento system. Uh, so we need to implement that, uh, some, uh, concept in there. Uh, just like, okay, we will getting the data information, uh, in admin section. What is the current version? We have a, uh, we have a implementing the 1, uh, admins admin section have the system configuration file for the creating custom access, and what is the current, uh, value we are facing, uh, right now from, uh, there. So there there have a multiple, uh, way for the doing this is, uh, automatically Magento upgrade mechanism. Uh, one is that we have a need to provide the Magento system administrator, uh, some configuration. Uh, that is that we will put the, uh, enter the current version. Uh, if it is a match in our database for the old version, uh, current version, uh, enable upgrade or not upgrade, uh, yes or no. Uh, field. Uh, if it is, sir, we have a, like, data, current current that match with the old version and new version. If it is related to that, it's a, uh, matching for the old version to uh, new version, then we have a going to, uh, not need to upgrade automatically. If it is, uh, not matching the suppose that old version is 2.4.6, and the latest version is 2.4.6 6 7. Sorry. Uh, 2.4.7, Then we have a getting some, uh, upgrade on that. So those so we will going part to the save that, uh, in database data, uh, for the latest version, old version. And going to the run the automatically command when we have a click on the submit button, that is a, uh, latest version and click the submit button on the admin configuration. Uh, so it will be upgrade. That's there are some steps we have, uh, uh, like, uh, take a backup before that. We have composer dot backup, then we have run the composer command, then we have run the, uh, setup, uh, d I compile, setup upgrade, uh, set up d I compile command, uh, cache clean, cache plus, uh, steady content deployments, indexer commands. So these are the things, and we need to check that, uh, there. And if we are talking about the security patches, so that's it. We have a using the AWS Commerce Cloud. So in their avail AWS Commerce Cloud is providing to the ECE tools. That is a responsible for the, uh, getting the patches. There are 2 type of patches will install. That is a, uh, one is custom cache. When we have a going to that, uh, just going in that of ecommerce websites and then check that is any patches will available. Then we have a going to them to hard fixes, uh, folder and, uh, run the some basic command just like setup, upgrade, the icon file, and steady content, deployment, cascade plus clean. So this is the one way for the install recover patch. And, otherwise, AWS Commerce Cloud is if you use the ECE tools, it is automatically we'll check-in the Magento Commerce Cloud. If it is there, any, uh, patches will available inside of where they are, then it will be going to that upgrade automatically, uh, and install the patches in our, uh, Magento cloud server. Uh, because we have a doing the, uh, latest ECE tools, so it's an every time when we are going to the release. Because the latest is happening on the so for the new feature, bugger is if it says or in, uh, update the functionality of the our application. So so we have using the EC tools there. We have a, uh, going for the, uh, in the Magento cloud and

So, securely, if we need to integrate, uh, the, uh, integrate our Magento store with the 3rd party GraphQL API securely, so, um, we will, uh, first, we will create the, uh, checking the first we will create the authentication, uh, process for the, uh, getting that data means so just like a fill login in there. Uh, so we need to use a name and password. So we will, uh, create first, uh, API for the, uh, getting the so for the login credential just like username and password. If it is a, uh, right candidate, then we have a create the token for the customer particular customer. And, uh, if it is a customer is a, uh, generated that in, uh, means register the user and the current generated the, uh, generate the, uh, data, uh, then we are going to that, uh, if, uh, token will If the, uh, will happening, uh, so, securely, uh, we will implement that first authentication, uh, process. Then we have a going to data, uh, connect with data, generate the token inside of it in, uh, devices. And that's then we have a going to that, sir, generate the token, then we have a getting that data just like we need to connect with the 3rd party API. Uh, uh, that's in the Salesforce dashboard. Then we have a getting the authentication key for the private key and public key, uh, for the API key, API secret key from the Salesforce dashboard, and, uh, we will provide to the our authentication in our application. Uh, then once we have created that, then we have created the, uh, token for the particular customer who's logging for the top party API. Then we have, uh, created the, uh, token generate the token. Then what we need to just, like, copy, we need to get, uh, the order create, then we have run the order, um, uh, GraphQL query, um, location. Uh, what is the requirement? Just like we need to send that or update the product price? Suppose they have a multiple, uh, product, but is this a suppose that uh, LoRaM is some, uh, uh, that's product in name in our website, uh, then we need to update the price. So we will, uh, send the, uh, write the query, uh, application for the sending the, uh, uh, that's been so that's we will sending for the application just like we need to update the product price for that, uh, product price. So we will, uh, take the, uh, and write the graph tool for that end, uh, condition. Uh, we will check that, uh, they have a, uh, that is a product test queue available, and that's price, what is available, what is the customer group is available. So there are some basic, uh, information we need to take from the, uh, updating the price, and that's product name ask you. Uh, then based on the SKU, we will upgrade the product. So, uh, price suppose $100 to 1 and $120. So we will update that by using catalog mutations concept. And, uh, suppose that we need to creating a pay up a custom product, uh, so he will be send that, uh, request for the all information, like first name, enable, disable, price, stock quantity, uh, that's product name, SKU, uh, price. So so there's some information we need to create a biog mutation, and that will be once we have a guard that, then we have around the gap queue of the query, uh, for the, uh, creating up a new product. Using for this concept, uh, to, uh, devise our plan

Okay. So if we need to, um, uh, maintaining this functionality and improve the performance. So first, uh, we need to get that, uh, get the, uh, select that only field. This is a required just like copy product ID, SQ name, uh, sorry, order order ID, order, uh, details, uh, price. What is the basic requirement? And we have a getting that, so select that field. Not not, uh, take the star, uh, because that is if it is an order, getting that software lost, topic collection on the order. Uh, uh, they are have a getting that. So, uh, so we will fetching that data. And, uh, so we need to, uh, use for the interfaces in these cases. So we will use for API concept. The interfaces create the repository interface and as API data. The respective concrete class of the model, we have a going further this concept, uh, we will, uh, speed up on our website. And that's another thing. So we will create the bonding cascade implementing our, uh, server. Bonding discuss will, uh, working as like a pay. Suppose one time we have a sending the request in with the, uh, first time, so it will be taking the, uh, 6 second. Then another, uh, time we are sending the same request, then we have a getting the 4 or 2 or 3 second. So by using Bonnie's Cassey, it is possible because that is a Bonnie's Cassey when we have a sending task. Means, uh, implemented the bonus cases in our application. So it will be create this on server, uh, before that's on a particular server just like a infrastructure of the Apache server. If we are talking about the database server, if we are talking about the Magento, um, course number, IP code, or what is available. Though before that, it will be created on the, uh, server. Uh, so first time when, uh, we have a send the request to the particular customer, uh, in application to the browser, uh, server. So once he will integrate interact with the Varnish case Varnish case is that if it is there, have a request is available for the particular, then it will be, uh, if it is available, then it would be going to the center response in the front end. It will not execute, uh, uh, zero number any number of line appear during this one. If it is a, uh, suppose we have a send that request and does not exist, uh, requesting the, uh, one is customer, then it will be going to the connect with our database infrastructure, uh, server, Magento codes, and, uh, creating the response of the particular request and, uh, in give to the response to the, uh, one. And one, this request and response will be stored on the is on server. And that's after that, uh, it's storing on the on server. It will be going to the front end. So next time when, uh, the same request will be arise and send for the customer, so it will be not going to this time to interact with the database or the executing the database queries and SMB. He will, uh, go into the warnings case server, check there if it is a will will available, then he will send to the same response to the browser without any number of line execution. So by using this concept, we have, uh, improved our performance in, uh, the that particular codes, uh, this one we and maintained our

So in this case, uh, we will use for the just like in there, we have implemented the background color color. So in this case, we have used for the list concept, uh, without not important, and styling will effect on the same, uh, purpose. Uh, so we will use for the, uh, list concept. Uh, so last concept is just showing saying, uh, if you have a want to use the list CSS inside of the our application, So you will need to create the, uh, state for the parent, uh, then that child, then that child inside of that child. And that means as a parent child concept, we have a using for their, uh, that's means, uh, parent class, we will introduce, then, uh, we are going to the child class, then we have a going to that child class. Uh, so by using this one, uh, we will implement there and create of a one variable inside of the top of the our dot list file. Uh, in there, inside of their list file, we have created this for the background color for the primary button. So we will create the 1, uh, variables, uh, just to install top of that. Uh, this is a button primary, uh, and, uh, provide the, uh, colors code. And this is a background color, so this is a background color. We have means we're providing the specific name of a primary button, uh, background color, primary buttons, so color, and providing to these variable and pass through these variable to the our, uh, classes where we have implemented to the parent child class inside of the our, uh, dot list file. And that's why using this concept, we have are not need to implement that important function, and that should be working perfectly for the anywhere, uh, uh, so looking that CSS code and determine that's not need to important inside of it because they are because that's we have using for the child class, then child class, then child class, then child class. So if we are using these concepts, so it will be not getting, uh, not lead to the important of that style seat and it will be uh, working as per per expectation without using the not important, uh, uh, class, uh, inside of your, uh, CSS. So this is the way, uh, we are using. That's another way we are by using the branch CSS than before the install in the grant on our applications. Uh, then we have a need to implement that, uh, grant or, uh, uh, CSS inside of where they are for the implementing the particular, uh, not important functionality. This is a similar to that, so, on the list, uh, but it is a more flexible, stable, the faster execution, uh, during to the when we have joined the grant CSS. So, uh, say, there are we have also used for the defined as particular, uh, in the top of the head of the particular custom grant CSS, and that's implement as a primary button background color, uh, color the color code of the variable, then this variable, we have inherited that. So, that's means by using this concept, uh, we have introduced that is not need to the important and, uh, also, we have a use for this functionality functionality to our current application without affecting anything. So and the, uh, main important of creating those variables, uh, for the top. So suppose these variable need to require further usable com, uh, compatibility, Uh, that's means these variable have required for the same color for the another places, then we have a use for the

So Magento system, uh, that's will, uh, architect Magento system that can revert back to a previous, uh, stable state, uh, post upgrade post upgrade while handling live transaction. So in this case, uh, my system, that's where we revert back onto the previous stable state than what we have are using for the same concept. We need to take that, uh, going to the uh, implement on the previous, uh, backup database in our our database server. Then we have a configure on the where our a n v dot p s p. Uh, config.psp. Uh, that's the username, database, and password. Uh, then we have a going to that, implementing that. So then we have a need to the composer run the commands, and we need to, uh, upgrade with the previous version. Then we have a going to dash run dash command, then it will be working. Uh, uh, rename the successfully once completed data. We need to change the h and every, uh, functionality, uh, because it is implementing data, uh, that with the old version. Uh, that means post updated version, we are going to that. So, uh, we will check that, uh, there. That's the, uh, that's so, uh, this is a very difficult to handling with the, uh, live transaction because of, uh, uh, when we have handling the line live transaction, so it will be, uh, case in this, our getting the difficulty for the, basic. So, basically, uh, that is that there are our 3 step for the means, uh, 2 or 3 function will, uh, authorize our process, uh, during to the, uh, payment transaction. Uh, so in there, we have a first use authorization, then we have a going to the capture. And that's, uh, honor will if it is a refund or cancel. So this is another part. But in there, have only for 2 is a method is a require for this, like, the transaction from there of the, uh, our application in version 22 just like a pay, uh, authorization. Uh, so it will be authorized that on the transaction. And once authorized, that will be up and going to the background system to upgrading to that our system with the stable version. Uh, and, uh, 1 once authorized that it will be captured our amounts from our application on the status of the, uh, premium methods, which one we have implemented that. Uh, so once it will be completed, that's, uh, prediction. Uh, in the background, we have also upgrading the post upgrade the system with the stable states. And that's, uh, been done to go for the so this is the basic architecture of the Magento system to divide on the, uh, uh, previous stable version and thus, uh, run the basic commands of the, uh, Magento setup upgrade, uh, setup DI compile, uh, steady continue pack as a clean class, indexing, re indexing. So after that, so, uh, running for the these, uh, type of a, uh, uh, basic commands, uh, then we have a going to check that functionality is working properly or or not properly. We have a going to check the place order. And that's, uh, these orders, uh, information will be coming inside of the admin section. Uh, so after this step, we have, uh, handled this situation, uh, with the live, uh, and live with the live transaction.

So, uh, when we have implemented the, um, uh, front end, that means, uh, mobile user experience. So that's we need to improve the optimized loading page in Magento pages. So, uh, basically, we have a, uh, talking about the Magento structure that's been so this one, we have a handling for the layout layout. So, uh, because there are a lots of customization in the front end. So we need to properly layout or describing the, uh, of the part particular on the Magento application. And apart from that, so we will going to thus use the implement the RPC full page. Uh, that means, uh, optimize the images, uh, CSS, uh, minified that c JS and CSS. We will use for the, uh, s three vacators will be automatically we have a add the functionality s t v bucket 2. It will be automatically implement as once we have added the product, uh, image inside of admin, then it will be automatically updated in the s SD with bucket server. So this functionality will be implemented, uh, and fetching the data from, uh, SD with bucket just like images. So this concept, we will use, uh, we will use for the, uh, DG compression, CDN network. We will, uh, reduce the third party, uh, web bundling, skip bundling, uh, binding. Uh, then we have a going to the use for the lazy load, uh, concept. Uh, we will implement, uh, that's been reduced, uh, remove the directly call while calling the code inside of the HTML file CSS. Uh, inline code of the CSS, uh, JavaScript code. We have implemented the inline. So these are the basic, uh, step of, uh, we will follow that in the speed optimization, the our website as well as of the mobile device. And apart from that, we will use implement the app. Apart from Memcasset, we will implement that. Also, Memcasset will be object memory is rendering the data. And best API, we have used for the, uh, then it is rendering the data too fast in the JSON concept. Uh, if we have, uh, implemented that, uh, memcast, so it will be getting the database requested query to the faster rendering the data, uh, from database. So this is how we will implement the main cache. Then after that, we have a going to that, uh, implement the radius cache in there. So radius how did we be re work with the radius classes. So we need to install that radius classes. So we will, uh, run some basic commands, uh, then, uh, just like a PPT gate to update, uh, install, uh, that's, uh, radius dash services. Then we have a need to write the nb.psp file inside of a ptcmb.psp file. Uh, so there, we will implement that, uh, nb.psp file, configure that our radius, uh, If we need to take a test how it will working or not working, then we have a going to the back a page case folder and delete that. And we have a going to the we visit on the home page and another page. If it is not getting the folder inside of a back as a folder of Webcast, it should be, uh, it's working perfectly. So, basically, what happening in there on the radius when, uh, our customer will enter our website, dvcstore.com, and that'd be a browser. Uh, then he'll interact with us, uh, controller helper, and JDSC install that inside there. So it will be created this one server before that on the custom, uh, our, uh, server. Uh, so once request will be sent, then if it is, uh, adjusting the request, then we will be showing for the in the front end.

Elaborate one your preferred tool and practice for debugging Magento performance issue on live site. So they are have a, uh, PSPCS, uh, we have used or the SonarQube, uh, we will use. These are the 2, um, best tools for the using for the, uh, debugging the performance. Uh, they have a, um, miss functionality. Uh, I we need to use further debugging the tools for the Magento performance in live site, then we have implement that, uh, Google page inside that the we have a going to that and test check our functionality. It means speed optimization, uh, means performance. We have another option for the GT metrics. We will go that, uh, implement that inside of the GT metrics. Matrix. Otherwise, the best tool is providing to that, sir, uh, Google Chrome. It is a lighthouse is providing to that. So we have a, uh, check that's our latest performance live action performance on the our application. So we have used for the Lighthouse inside of the the Google browser is providing to the if you are going to the inspect element, it's providing the lighthouse application. So it's, uh, mainly used for the your what is the exactly page speed on the your performance you want to live track on the BioGEN Lighthouse concept. Uh, so we will check that where it is getting stuck, what we need to performance to improve that. What is the steps of, uh, we have reduced the, uh, CSS, JS, GP, g g for or we need to implement the CDN network, or we need to implement the some mini files, CSS, their JavaScript mini files as a file. What is the how much your extension we have used for their and that's, uh, unused extension, uh, are the, uh, uh, that's we have a because that's in Magento to use the user of the application. There are a lot of extension already installed on our application. So we need to check that and verify that's, uh, which extension we need to use that, which is a perfect utilized for our application. So we need to go for this type of a, uh, uh, step so we will, uh, verify that, uh, data, uh, performance in the live site on our production server. And there, apart from that, so we will go into the implement the radius case a, uh, the, uh, uh, that's for the performance, check that. And, uh, another thing is that we need to using for that, uh, lighthouse. So, uh, implement that is a lighthouse is our light to uh, light tracking. And that's another another we have used for the New Relic options. And, uh, uh, we this is the best one option. We have a New Relic, uh, and Datadog, but I will, uh, go for the, uh, best option. Compatibility, flexibility, consistency, and maintainability of the our application. So it will be providing to the as like of a, uh, customer tracking information, your live, uh, performance of the your Magento application. What is that exactly? And it is also provide the specific type of pages, what pages it should be, uh, getting the speech, uh, performance in there, uh, or we will go for like that. Uh, we have a a suppose we have implemented the small widgets and getting the, uh, taking the loss of a, uh, speed or, uh, performance related issue. So it will be also also we will track for the particular widgets option, um, because this is a very flexible user to provide the New Relic concept in our modern 2 application. So it is the best way we have using for the, uh, dividing the