🔥 Laravel Tip #82: If you have multiple Laravel apps running on the same server, make sure to configure a unique APP_NAME in your .env file. This will immediately help you avoid cache, session and Redis collisions.
🔥 Laravel Tip #81: It's generally a good idea to check if your dependencies are compatible with your project in terms of licensing. Composer has a command to do this easily. Enlightn also takes care of this for you! 😎 Learn more: https://t.co/IjtP7CLDRR
🔥 Laravel Tip #80: If you invoke multiple Redis commands in the same request, you should use pipelining to increase query throughput and reduce network round-trip time. Laravel Horizon extensively uses pipelining to improve performance. Learn more: https://t.co/8K6PDUvMDB
🔥 Laravel Tip #79: To avoid render blocking JS, consider using async or defer attributes. Use async for independent scripts that require early loading (e.g. analytics). Use defer for scripts that need the DOM or need to execute in order. Learn more:
🔥 Laravel Tip #76: Don't write your own code for security features unless you can afford penetration testing it. Consider the following code that allows user enumeration through timing attacks. It's very hard to detect these in a code review, so don't risk it!
🔥 Laravel Tip #75: If you have some routes and jobs that hit the same rate limited API, Laravel provides you the ability to share rate limits!
🔥 Laravel Tip #73: If you retrieve multiple items from the cache in a single request, you can use the "many" method to retrieve all of them with a single network call.
🔥 Laravel Tip #72: WebP images can improve performance by quite a bit as they're about 25-30% smaller. However, browsers like Safari have only added WebP support to their recent versions. A way around this is to detect browser support and serve content accordingly.
🔥 Laravel Tip #71: For improved performance, try to sort your queries by an indexed column rather than a non-indexed column, whenever you can. Here's a classical example of this:
🔥 Laravel Tip #68: It's a good practice to set password strength rules and also ensure that the password hasn't been compromised in data leaks. Thanks to @enunomaduro, today's Laravel release will include a Password rule right out-of-the-box!