
I aim to pursue a vibrant career in Information Technology, seeking an environment that fosters growth and continuous learning. With around 6 years of experience in web development, I am committed to contributing to the advancement of the organization while cultivating a long-term, mutually beneficial relationship.
Senior Engineer
Cambridge Technology Enterprises LimitedFull Stack Laravel Developer
PacktSr. Software Engineer
Commerce PunditPHP Developer
iFlair Web Technologies Pvt. Ltd.PHP Developer
Hyperlink InfosystemJira

Envoyer
XAMPP
Hi, I'm Ronok Solengi. I have around 6 years of experience in web development and the entire software development industry. I completed my best computer application in 2017 from Bhanagar University, Gujarat, India. Since then, I am working as a software developer and a full stack developer for around 6 years, and I have expertise in PHP, Laravel, Vue.js, and Next.
Yes, I'm aware of subqueries. We can write it using a Yellow account or query builder as well, to explain why we need that. Because sometimes we need to get some data from another table. And based on the results, we want to get data from our first main table. So that in that case, we need subqueries.
I developed a Laravel application as a middleware for external ecommerce systems, including Magento and software, to import products from Magento and send them to our software. To import products from Magento and send them to our software, I also got orders from the software for customers and sent them back to Magento. In this case, Laravel was used as a middle part to manage the import and export of products and orders. I added a middleware to authenticate the external APIs, including Magento APIs and software APIs. For routing, we implemented web routes, API routes, and console routes mainly because we were doing many things using artisan commands. To optimize performance and scalability, I used a queue so that everything happens in the background without needing admin intervention in the Laravel middleware. Regarding performance, I tried not to use Eloquent because it's not well-suited for performance techniques when dealing with the database. To address scalability, we used a microservice architecture, which allows for better horizontal and vertical scalability in this way.
JWT is very secure because it uses auth and is directly stored on the server, and we do not know the exact token string. So, it's more secure that nobody knows the exact decrypted string.
To secure sensitive data in a Vue.js application, we must make sure that the ENV files are not accessible publicly. We should bill in that way and do not store sensitive information in local storage or session storage, that might break the security. So we can use Vuex store management to keep such sensitive information in a secure memory.
We can use a CSS preprocessor like Sass. We can also use Webpack to bundle and serve as a minified version.
Lava will fortify the authentication for the single-page application mainly. I'm not sure about that.