Strong OOP, Design Patterns, MVC, SOLID principles
Database architecture, MySQL, abstraction layers
6+ years in Magento 1.x & 2.x (CE & EE),Laravel,Core PHP deep functional & technical expertise
Performance optimization, scalability, enterprise infrastructure (AWS)
Strong experience: Zend Framework, JavaScript (JQuery, AlpineJS, RequireJS, KnockoutJS)
CI/CD: AWS CodeDeploy
Version control: Git, GitHub, Bitbucket,
Web Services: REST, SOAP
Software Engineer
InventionStar IT ConsultingSoftware Engineer
Tridhyatech Pvt LtdSublime
Notepad++
Git
AWS
Composer
Knockout.js
HTML/CSS
TypeScript
Next.js
Laravel
Yeah. Hi. Myself, I'm having 5.5 years of experience in Magento 2 gig development, custom extension development, team integration, and, uh, API development. And I have worked, uh, in multiple projects, including API integration, team extension, development, and yeah.
So for to identify memory leak in Magento 2 application, uh, I need to check a custom module and then, uh, debug it and fix that memory leak.
For that, uh, we need to, uh, create a maintenance flag on original site. And, uh, for that time, we need to redirect that original site to other website, which we can use temporarily as a live. And, uh, after completion of maintenance, uh, we will redirect that to originals. So it will create a zero downtime deployment for live high traffic, uh, Magento to website.
So the key points for responsive here in Magento 2 are, uh, need to check, uh, with, uh, different browser compatibility, check device compatibility, and also need to check, uh, packages list, uh, which we can use in, uh, feature of greatest in the show Magento version and, uh, responsiveness obtained. And, also, we need to ensure the speed optimization in the responsive.
So after post launch, uh, if there is any critical bug, then we need to set a website on a maintenance mode and check the logs for, uh, trailing of that particular issue. And we need to fix, uh, that error as soon as possible because it's a live environment. So or, also, we can use a different approach. For example, uh, we can solid on production or, uh, they'll server first. Sorry. They'll server. And then after successful testing, we can apply their those changes on live website.
Okay. So whenever we are developing a customer custom module to follow the NVC design pattern, we need to create controller view file, uh, for front end, and if required, then admin's channel. And we need to create a model if we have any custom table in our custom extension. So based on that model, we can apply that MVC pattern in a custom model. So model is responsible for the business logic related to database. You is, uh, responsible for front end, uh, UI interface, and controller is a connection between model and view.
So this query is related to sales orders. So there is
So for a custom product type, uh, development, we need to add a custom extension. And that extension, we can add a product type. We can use the f r s of Magento catalog model and uh, check how it's adding those default products in bulk control bundle, etcetera, in Magento environment. Based on that, we can add, uh, our custom product type, our custom extension, and use, uh, develop the required code to ensure the, um, checkout flow order flow and other required
Yes. Uh, to set up the project in AWS server or Ubuntu server. So developer need to learn the those required commands to move the files in proper directory to install the required extension and configure to MySQL and require a back end server. So, yeah, it's, uh, useful to run the browser the ops commands and do that for the ops practices. It is very useful to all of it.
To implement and ensure the security of user data in Magento 2, we need to, uh, enable the CAPTCHA. We can use secure password in admin side And, uh, do not, uh, use any third party login extension. So, yeah, that's that is very useful tool and sort of a security of user