Ranjit Patil

Hi. My name is Ranjit, Grou. So, basically, I belongs to Pune, and Maharashtra. So I do have good commands on, like, PHP core PHP Laravel. MySQL, WordPress. WooCommerce, So I do have experience of, like, 8.5 years into this skill set. I was working with X1 Solutions on the recent organization since last, 4 years, like 2020 till 2024, 28th June. So, basically, like, I have, Also, mostly worked on, like, open AI development where, like, we have, trained the model via API and then, we have done the fine tuning We have, directly, send the prompt to model and then are the response we were getting. So we have trained the model in such a way whatever the request or the prompt has been fitted to the model, we'll be returning the JSON. Format, and that JSON format we have encoded within the, like, short handled code understanding. And based on that, we have, created the multiple kind of affiliate programs and all. So, where, like, product suggestions, and, like, applying discounts to the to the, people if they are simultaneous search on the same thing, then we have enabled 1 more gateway there. They can pay the, half payment and then part payment needs to be done. On after month. So this kind of addition functionality, we have enabled via open. Yeah. So recently, I was working with Lee, Laravel for creating SaaS. So, basically, QuickBook. Io, we have created 1 SaaS, which was, the open platform, has been created where, like, if any full commerce or Voodoo or, we can say, like, Shopify will be getting created any orders that has be directly sent to QuickBooks. So, this kind of a feature we have developed and based on the the entity consumption for like, if the customer is using, like, 1, 000 APIs in a month, So based on, first 100 APIs we have sent, set very free. And, onwards, like, we have charged each API, like, point $40, point 40, dollar for each, kind of a. Like, each kind of a transaction, entity transaction. So it will be creating the multiple, billing platforms where, like, we have enabled and switched the panel as well as we have enabled the Razorpay gateway over there. Make the subscription as well.

So, um, back end PHP service, I can say, like, uh, for instance, there might be, uh, several factors where, like, uh, web service is in the old, which needs to be, uh, mannered in very, very structured way or where a very principal prototyping followed, uh, while creating those services. So so, basically, like, design pattern is nothing but the normalization and, uh, the pattern which needs to be very clear and crystal clear and easy to understand to other people to contribute on that. So that according to me, that is the design pattern or design principle I have principles, I can say. So, basically, while creating kind of, uh, additional lengthy functionality or, like, very clutches functionality, we have to, uh, follow the object oriented programming where, like, uh, namespaces, classes, trades, uh, has to be used, uh, where, like, auto load has to be used for if we are using the multiple libraries. So, uh, this kind of set parameters are there, uh, as well as, like, we have tools to provide the commands, uh, kind of, like, rate limiter and all, which which, uh, automatically enables the usage of that particular API or the particular services. Uh, along with this, I can say, like, authentication and authorization needs to be managed in very, um, appropriate way. For an instance, like, if admin is getting logged in and then he has not, uh, he does not want to have all the control, uh, so he can delegate few of the models to, uh, like, super admin. So, basically, this kind of authorization needs to be done. And for maintaining this kind of authorization, we need to have the very factorial, uh, factorial, uh, coding standards where, like, PSR, uh, coding standards needs to be PRPSR, uh, principles needs to be followed in very certain manner. So, uh, cookies and cache needs to be very stored in such a way for instance, like, uh, that has to be very mapped with user or specific model as well. For instance, like, if for login, we are creating multiple sessions and cookies. So within login, we have to, uh, within login, we have to pass, like, uh, uh, array, uh, for each user, and each user will be having that certain set of parameters value into a single session. So this kind of a certain, uh, design prototyping of, like, coding standards needs to be maintained to to have a flexible, uh, flexibility to others as well to contribute on the same.

Yeah. So in PHP within PHP, there are, like, certain kind of debugging procedures. For an instance, uh, we we have, like, custom error handling or exceptional handling, uh, like, try catch blocks out there, as well as, like, if we want to debug any kind of bottlenecks or for an instance, like, there will be a max max execution time or error for single functionality, which is going into loop and loop. So it will be automatically stop the server or it will be automatically stop the page to serve. So, basically, in this kind of a feature, like, uh, in this kind of a scenario, we can have the debugging with, uh, print, uh, request. So based on, like, print request, we can identify whatever the breakpoints are there and that breakpoints are unable or not. So based on this, like, code execution, we can have this kind of a certain, uh, aspect to as well as, like, control or the code as well. So this has to be used. Uh, but, like, in, uh, from my experience to, uh, from last 8.5, so exception handling has to be very, very, uh, has has played very, very good role into this. So till and until, like, we are not providing the exception handling, the the code will not, uh, will not work into, like, what are the expected manner we were expecting. So for instance, uh, like, recently, I have worked on 1 of the client where, like, he was he was using the Zoho integration API. So, basically, like, they were sending 1 request to Zoho, and then based on the Zoho response, they were, like, uh, operating the other parameters or other models. So, uh, functional making this functional based on, like, exceptional handling is very, very, uh, very effective. So if the response is getting empty, so there is no way to point out the next module to be run, uh, because, like, uh, that that model doesn't have anything to, like, perform the actions and all. So this kind of, uh, additional exceptional handling needs to be, uh, very effectively, uh, done as well as, like, logs has to be maintained. So whenever we are creating any kind of functionality, uh, if the functionality gets failed so that a log has to be maintained in certain files or somewhere, like, uh, we can track a little while debugging and fixing the code.

Yeah. So, uh, basically, there are there are multiple ways to optimize the SQL query. From from my side, I think, like, uh, there were the table which were, uh, having around, like, lacks of records. So, uh, select query, obviously, that won't work. So, uh, there are multiple ways to function this. So, basically, first way, which is very popular to have the indexing, uh, to to particular table. So indexing, there are, like, 2 stages as well, like, within the QD indexing or the table indexing. So, basically, like, if we are indexing the table, that that will be the permanent, uh, uh, whenever we create or whenever we insert any records, so it will be automatically considered at the indexing column and all, whatever we have mentioned. And, like, on on based on the QD execution, we have also, uh, we can also provide the indexing for a particular, uh, particular column based, uh, based on the QD execution. So for an instance, like, 6 star from, like, table name, and then we can, uh, index the column. So that is, like, more operational way. For an instance, like, 1 table does not have always the single entity, uh, has to be indexed. So next time, the same table might be having the other column as index. So, uh, the temporary indexing, which can be done via SQL query, is more relevant. Uh, also, like, normalizing the table, basically. So normalizing, uh, the table can be defined as, like, very, very, uh, very pro manner, because, like, if the table is very normalized, so query obviously won't get conflicted. Writing the sub query, uh, we need to avoid the right, uh, writing sub curies till and until it is required. For instance, like, if we are joining few kind of tables and then we are returning the single records. So, uh, for instance, uh, there are 3 tables like employee salary and then employee details. So this has to be, uh, into a very normalized way. So when we write the QD, uh, that will be performed, uh, very fast if it is normalized. If it is not normalized or not organized, to write the query, and then again, it will be getting more complicated.

Yeah. So for in for recently, like, uh, I have I have learned the the the materialized, uh, materialized design long back, like, 4 years ago. So at that point, I have I have seen the the aspect or the usage of, like, SCSS, uh, is is more more used or we can say, like, highly scaled. So, uh, another we've, uh, for an instance, like, we have on CSS, which is, like, having the multiple lines and, like, uh, very, very refactor, uh, refacteral manner. So that has to be converted into SCSS, which will turns really very fast, uh, as well as, like, that has to be very in segregation way. For instance, like, a single file is there, which which will be having, like, 2 to 4 models UI. So that is not required yet, uh, because, like, anyhow, the first window or the first model on the single screen, the single model will be served. Uh, our single tab a single model will be served. Till and until we are not customizing or not, uh, having interpret within the models 2 models. So, uh, uh, whenever the single model is getting served, that particular CSS has to be, uh, into a separated way for an instance. Like, model 1 has to be, uh, model 1 SCSS and model 2 will be having the model 2 SCSS. Will it dead very dedicated? And the common functions or the common classes or the ID CSS has to be moved to, like, global CSS. So this can be a good approach, um, because, like, I have used, uh, for SaaS as well. Because, like, SaaS were having, uh, um, around, like, 70 MB directory. So in the where, like, around 175 models has been created, and, uh, I have created the separate separate model, submodel, parent model, then based on this kind of, uh, direct structure, I have created the CSS, and then I have called them based on the on the model names and all. So segregation of the CSS has to be very very first approach, uh, while while, you know, like, having the large CSS code based optimization. And second will be, like, uh, the the SCSS CSS to SCSS conversion or single line CSS conversion or minified CSS conversion needs to be done.

Yeah. So I think, like, the core PHP or the or the very vanilla PHP application, we'll be having, for instance, like, time load of, like, 7 to 8 seconds. And when when we move to Laravel, like, it will be again, like, short shorted to 2 seconds. So, obviously, like, Laravel will be having this very structural manner or the pattern, uh, of, like, code, uh, code declaration and all. So, uh, so there are certain steps. So, basically, like, according to me, first, we have to convert all the all the UI within the model, and then each model has to be, uh, like, called on different models based on their relay relation. And, uh, as well as, like, we have to we have to keep in mind that what are the, uh, microservices or, like, auth, uh, related APIs are there, that has to be added in in route. So first, like, first approach is to create a model and then, uh, approach will be, like, creating a controller. And, uh, and then, like, last 1 will be the creating, uh, APIs within the route. So, uh, this can be done, but this is the kind of very hectic way because, like, it might be requiring the migration. It might be requiring the cedar. It might requiring, uh, the the, uh, the design common, uh, common related libraries and all. So yeah. I mean, like, that can be done, but, uh, in in very sorted manner, uh, we have to keep in mind, like, model and then what are the APIs it has to be registered. So, uh, this can be done, uh, within this, like, pattern. Uh, also, I would like to add 1 more thing here. Like, recently, I have done that. So 1 of the plug in, like QuickBooks, uh, connector that we have converted to, uh, 1 of the Laravel SaaS template. So while converting, we found that multiple, um, multiple kind of user relation tables has been already there. So those entries has to be considered while migration, uh, while migration and all. So cedar has to be maintained in certain way. So, uh, yes. I mean, like, by by performing multiple, uh, principles that, uh, can be achievable in very, uh, very short and short and time as well.

Yeah. So, uh, I think, like, user is the user is is kind of, like, 1 of the model which has been created while creating a migration and all. So user, uh, variable in the first line, I can see the user variable will be having all the users details. Uh, all the user rules will be considered. And based on the user rules, the forex loop has been created and then user, uh, will loading user load post. So what are the post has been created for user rule that has, uh, to be shown or that has to be binded very well. So in this, I think, like, has a property, uh, like, like, have property or, like, have a property some call call of a property has to be, um, maintaining, uh, in a relationship manager. So relationship manager, I cannot say relationship manager because, like, has property because, like, post is already 1 of the table. So that table has to be mapped with users. So, basically, like, each post table, uh, sorry, post table, each row will be having the user ID. And based on that user ID, that has to be mapped whether the user, uh, is within the loop. So, basically, like, uh, user has post can be a solution on this.

Yeah. So singleton application or singleton function, uh, or singleton pattern can be considered as, like, the instance has to be declared or, uh, initialized or appended, uh, only within the class or the ones we can say. For an instance, the the code, uh, which has been given will be having the private function construct. So, basically, like, uh, the construct will be preventing the the other instances. So, basically, uh, for an instance, uh, whatever the construct construct, uh, will be containing, like, initialization of the variables and all if if entire directory is used with the multiple variables. So that variable has to be maintained into, uh, private construct. But, uh, that should not be, uh, or even the the singleton, uh, instance.

Yeah. So, uh, microservice in Laravel, uh, for for ecommerce, I can I can see, like, there will be, like, certain parameters called products and then product relationship, uh, schema has to be designed? And then product will be having the categories and then subcategories and variations, and each variation will be having the attributes and all. So, uh, like, for an instance here, we can consider as as WooCommerce where, like, multiple APIs has been provided by WooCommerce. So considering considering multiple APIs of the WooCommerce will be used for Laravel, like like, uh, Laravel design and designing all the structure architecture. So, uh, we can we can create the multiple models for, like, you user and then product, uh, for, like, for product, it will be having the multiple screens, like, uh, the cart, then single product page, checkout, order, uh, and then shop page as well. So, like, within the single model, like, multiple, uh, sub models will be created, and sub models will be, uh, having the the data by using the microservices. So it will be, uh, for instance, like, we have created a microservice for card. We have created microservice, uh, service for checkout. We have created microservice for order, uh, by adding the middleware of user or auth, we can say, for a particular log d user only that these microservices needs to be served. And, uh, for shop and all, uh, or for a single product page, microservices, I I don't think, like, uh, microservices need the middleware, like auth and auth. Mostly, it will be, uh, returning all the all the data.

Yeah. So real time synchronization, I can say, like, with the Ajax as well, we can do, basically, like, for instance, for for instance, just consider, like, if we have a search bar where, like, a single page where multiple, uh, 1, 000 of products has been displayed. And then, uh, at the at the admin side, the admin is getting, uh, added the products, uh, simultaneously. So that has to be reflected on front end. So in this, like, uh, what whenever the admin is creating the product, that has to be set to SQL. And then, um, from the SQL, each each time that data has to be fetched very frequently. So without WebSocket, I can say, like, we can add the timers or something called, uh, or, like, Kron, we can do. So, basically, like, on based of Kron, with the with the interval of 1 minute, the Kron will go to database. It will read the record count and the the existing count of the the another, uh, loaded side. So we can see, for an instance here, we can consider, like, 1 screen is there. On screen, like, we have, uh, we have calculated the count of current products and set it to session. So here, like, on AJAX or on Kron, we'll be containing or, uh, we will be getting the count of session and count of, like, uh, SQL queries. So if the SQL will be having the 1, 050 products and session will be or the state will be having the 1, 000 products. So the 50 products are the difference, and then it will be counting the 50 products more. And then it will be syncing to, uh, again, like, uh, session and all, then that can be done with the AJAX.