Harish Thatikonda

Could you help me understand more about your background by giving a brief introduction to yourself? Yes. Myself, Harish, and I'm from Warangal. And, uh, in this, like, I I have started, uh, working on Magento 2 from company Kinzum Solutions, where I have worked on their own their own, uh, product, which they have created by the Kansan peoples, which is like connector, uh, which integrates between Magento and Acumatica ERP systems, which, uh, which provides a, basically, a bidirectional syncs between Magento and the Acumatica ERP system on syncing these customers and products and everythings. And and I have worked on many projects, uh, basically, basically. Um, in the string, I also have worked on this connector related product and, uh, mid Atlantic. And, uh, there is American images, which I worked on in project. And, uh, in coming to I have again, uh, started working on, uh, d a digital where I have completely worked on vision to front end and back end related things. So back end, I have worked on, um, most of the destination products, destination pet, and, uh, this, uh, SHRM. And in front end, I have worked on, uh, c p h related stuffs. From the scratch level, we have created the c p s site, which is, uh, previous ID is aem. So these are things we have, uh, done more on these projects.

Share the method to effectively debug and resolve a complex issue that arises post deployment of a Magento 2 extension. Oh, basically, uh, complex issue that arises. So, basically, we need to debug, like, uh, if there is any issue. So we need to check that model naming conventions and model declarations has been given correctly and, uh, check what are the codes we have written or if there is any loggers we have written that, uh, that trying to log, uh, huge data. Right? And, uh, if there is any test cases, we just need to verify, like, if the test cases are working fine. And if there is any, uh, then we need to check, like, uh, what are the capability of the code we have written for that extension, which we have deployed for the server level and what the servers, uh, like PHP version and compatibility has depending upon this, uh, version 22 extension. So we can check this, uh, if there is any errors in this exception dot log or or in, uh, debug dot logs system dot logs. So we can get some information from there and figure out if there is any issue and what is the issue facing. So some points I have mentioned, like, we can check using these things. Or, like, we can also, uh, create 1 enable or disable configuration for this model, and we need to check, like, uh, from is there is issue from our model itself? Then we need to figure it out, like, how debugging into the code, like, from the registration model at XML and from the d at XML and from where it is coming and from there it is treating. So we need to go by step by step, Anthony. Not we'll just, um, enable this model and go with the functionalities.

Discuss how to design a fault tolerant system for image and to to store fault tolerant system. Basically, uh, if we are doing any deployments or anything and, uh, if you are able to see, like, some type of, uh, issues are occurring on every time. So to recheck, like, before or after the production deployments, you you may see some type of factor code issues or anything we are seeing. So we just need to uh, basically, we can do some type of, uh, testing related things, or, uh, you can also, uh, create some Lambda test test where we'll which will be executed after the deployment and figure it out if there is any issues or any breakdowns in the site level, which helps us to give the reports. And, uh, based upon the report, if there is any breakage of any feature, Some minimum features which we can plug so that we can fix those things. And, uh, the availability is, like, uh, we need to hit, like like, IP allow list. We need to thoroughly check, like, which IPs we need to allow and which we can list this. And if you are using any one is related to caching, click, then there we have, like, um, IP restrictions. We can add the restrictions or IPs, which we don't want to allow them to assess our site store. And and the URL should be, like, secured, and, um, there should not be any data leakage. So everything just we need we need to take some type of backups, actually, so that if there is any issues with the, uh, some current after the changes, if they if anything goes wrong so that the backup database related, uh, things we can just again revert them, and, uh, we can make use of them instead of waiting instead of wasting more time in debugging and, uh, making the production server down.

So, uh, we can upgrade the Magento version from the old to latest. Basically, if, uh, if the Magento is completely handled by the cloud related things, like, uh, the ecommerce, uh, the way related cloud things. So, basically, we may keep, uh, raise a ticket to them, like, uh, to check tech to check with them that, uh, how we can ask them, like, please upgrade the image into some older version to latest version. If not, then we can upgrade using composer from the nonlocal systems directly or from the cloud level. So we can just use the composer, um, upgrade little commands where we can need to update the composer dot JSON file using composer command. And, uh, after that, we just need to hit the composer update so that the latest updated version, which is added into the composer dot JSON file, We'll update, uh, the all the Magento, uh, related things, everything to the latest version, which is mentioned in the composite dot JSON file. But that we just need to run all the set of operator, uh, comments to check whether this IT is up and running.

Outline a solution for safety implementation, a zero downtime deployment strategy for a m agenda to store. So, uh, we can just minimize, uh, this, uh, deployment time, actually, uh, using, like, merging the CSS and, uh, less files. All these, uh, JS files matching them. And, uh, you can create, uh, deployment, uh, in a different strategies. Like, uh, we have, like, a different, uh, type of, uh, enterprise versions. Like, we can purchase there so that the support will be given for us, like, the minimum zero time downtime deployment strategy. So and we can also reduce the deployment time, the meeting the CSS and the JS related stuff and, uh, check these things, like how can we optimize this more as much as by, uh, doing some type of removing some type of models which are not necessary. And, also, like, uh, the zero downtime deployment strategies. Uh, these things will come, like, uh, basically, in the configurations level. We can use, like, we can, uh, basically, by bringing down this deployment time to very less time, like, 5 to 10 minutes like that. So it really doesn't make any changes in the deployment, in the production, or some type of things. Depending upon the cloud, uh, configurations, these zero downtime deployment strategies will work and also the, uh, optimization of this CSS and, uh, JS files.

What strategies would you use to insert image entity extension you plan to develop others to the solid principles? So, basically, we just need to, uh, do this, uh, development in a exact and particular way, coding standard as per the Magento coding standards. So we just need to follow all the standards, and, uh, there is also we have, like, uh, tools where we can, uh, check our coding standards of this model, like, how this, uh, Magento coding standard follows, which is, like, object oriented programming language on the gen framework related things, how it is going to be used. And, uh, based upon the Magento coding standards, we just need to create all the necessary files, which is which are like a etcinmodal. Xml.phv. And then other, if we are adding any, uh, web APIs, then we can add a web API dot XML file in etc and repositories API and, uh, model files. And if there is any grid, the grid level things, we can add it in the layout and, uh, a UI admin grid. And, uh, so, basically, there is also, like, Magento coding. Uh, there is also, like, tool where we can check these coding standards of Magento using this Magento, uh, Magento coding this magento coding standards check tool, which we have with GitHub, and, uh, where we can use PHP CS PHP CS snippets, like, to check what are the errors and everything. So, basically, we just need to, uh, do the codings based upon the Magento core functionality and principles where we can add all the doc blocks and everything. Even you can check this the, um, the code which we have developed is are is correct, accurate, or everything directly in this using this, uh, SonarQube and, uh, these tools, uh, gives us some errors if there is any, uh, issues with our code or if any, uh, principles we have violated.

Examine the JavaScript code. You should for Magento front end. Can you spot the error that might affect the functionality related to the Magento's checkout code? Can you spot the error that might affect the functionality related to measuring test checkout? Can't see any code here. So, basically, we can, uh, we can check this JS files or JavaScript related code, everything. Uh, if if you see any errors in the check code page, we can check-in consoles, or we can add any loggers in the JavaScript file which, uh, we have added. And we need to figure out, like, what is going wrong. And, um, we can also check, like, the updated JS file is present in the store level or this old one. You can directly check that, uh, JS file's code in these, uh, using debugger tools. And, uh, we can figure out, like, how we can, uh, fix those things. Basically, we can check-in consoles related things, the errors we can get, or we can add some type of loggers, and, uh, we can figure out, like, how we can fix those things.

Consider this code sample for creating a new Magento extension. Identify the potential issue with this class when othering to match into best coding practice. Basically, the class name should be like should not be like the custom model underscore plugin underscore product. It should be like, uh, some type of naming convention should be correct, which should be, like, uh, any class. Like, if you are wanting to modify the products, then we can give the any before product class or something like that. Instead of being custom model underscore plugin underscore product, that we can do. And and I see this before get name, there are 2 2 slashes in dimension 2 catalog model product subject. Maybe this will be some type this is issue. Like, we should not give, like, this depth. It will be, like, medium to catalog model product type. And, uh, before, uh, get name, this is, like, before plug in name. So our logic is here. And, uh, the other related plug in methods, we can write below. Basically, we need to check these class names and, uh, the dependency thing which we have given the subject related thing so that we can, uh, customize the related product name and return them.

How would you approach the optimization of heavily overloaded Magento 2 database that is critical for business operation. So, basically, we just need to, uh, check, like, uh, if there is any previous data which is storing in our database, which are not required. Like, if there is any products which we have deleted or deleted related reviews or any related data for those products, We can remove them, and, uh, we need to check if there is any query log is happening. Uh, and we need to check, like, if there is any crones which are creating more, uh, impact, uh, load on database related things and to figure it out, like, how we things are affecting this. And we can check, like, a better way so that the queries can be optimized, like, the, uh, cache related things are enabled or not. Basically, we just, uh, need to remove the unused like, unwanted data, which are not required for our store level. Like, if there is any previous data which we deleted but still present in these informations. So we can delete them directly so that it will give some space and some decrease some load on the database level.

What approach would you take to customize your image into to store? Timer. Team for optimal rendering on mobile services. So, uh, optimal rendering on mobile devices. So, actually, uh, we can write, uh, these, uh, themes related, uh, CSS and everything using this, uh, depending upon the mobile devices. So we need to add these CSS related things in app design theme level theme folder. Suppose if we want to add any if you want to extend the theme and we can write, then we can directly in the app design level, we'll just create this theme folder, and, uh, we'll just add the CSS files, which we want to, uh, uh, less files, which we want to add some CSS to mobile devices. Suppose if any mobile device is selected, then the CSS using this, uh, list files. We can just optimize these screen widths and stylings and everything so that it will be uh, updated. It will be updated, like, uh, what are the based upon the device, the CSS, uh, the screen which and everything will be updated accordingly. User can have, like, a good experience on the device level. So we have this type of, uh, feature. Like, we can write, uh, CSS for different different devices using, uh, min width like that.

How would you utilize MySQL's transactional support to handle rollback scenarios for a failed data? Important Magento. Basically, uh, we need to check, like, like, which tables where the data is getting. So we will be having this rollback feature, like, when, generally, if any table has been dropped or if any data has been deleted using this MySQL rollback feature, we can just get this data directly if that, um, rollback feature is enabled. But if it's enabled, then it may create some type of load. So, basically, we just need to be fully prepared. Like, if any things may happen in different different scenarios, so every time we just need to take a backup of the databases when we are trying to do any deployments or anything so that if anything goes wrong, then the old database can be reverted back into the same place instead of, uh, breaking down the production services. So and, also, we just need to check that MySQL is running in a correct, uh, good, healthy, uh, state if if it is not creating any load impacts so that, uh, the imported data can be added directly into these tables. If the load is heavy on the database level, then the, uh, input will be failed because of this, uh, heavy load in this. So we just need to, uh, check everything that, uh, the things are in cart pay before importing these things this, uh, And I also checked these ground related things, which are working parallelly for importing things. The consumer if there is any consumer hitting this, uh, SQL, um, database for inserting this import data like this.