Describe what you are calling a big company.
Fedex = thousands of transactions daily = big.
a company with say 20,000 records total is not big (as far as a database is concerned). As far as security goes laravel is good, but you need to understand programming in security with or without laravel: https://www.owasp.org/index.php/OWASP_PHP_Security_Project Study this stuff.
jimgwhit said:
Describe what you are calling a big company.
Fedex = thousands of transactions daily = big.
a company with say 20,000 records total is not big (as far as a database is concerned). As far as security goes laravel is good, but you need to understand programming in security with or without laravel: https://www.owasp.org/index.php/OWASP_PHP_Security_Project Study this stuff.
Exactly. Whatever you decide fghorbani, vanilla or framework I think security and performance should be the biggest questions moving forward. You know what I mean? I would be looking into api's and how you are going to serve the client end. Validation with Laravel is easy but how are you doing it on the client side, because there is probably the biggest performance gains. Minimizing scripts and limiting http calls when applicable. Also I would look into caching if I were looking for better performance, and then go to debugging the php. Did I help?
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community