Posts tagged with caching
– youtu.be - submitted by Bert De Swaef
In this episode of the Quick Win Wednesday series, I'll have a look at how to use flexible caching in Laravel. A great way to avoid unhappy users who'll hit invalid cache.
Read more [youtu.be]
Some interesting thoughts about caching.
Read more [buttondown.com]
Join 9,500+ smart developers
Every month I share what I learn from running Spatie, building Oh Dear, and maintaining 300+ open source packages. Practical takes on Laravel, PHP, and AI that you can actually use.
No spam. Unsubscribe anytime. You can also follow me on X.
– aaronfrancis.com - submitted by Aaron Francis
Transforming and serving images from Laravel in a cache-friendly way.
Read more [aaronfrancis.com]
Learn how to use GitHub Actions to speed up your Deployer deployments by cleverly caching your frontend build assets
Read more [stefanzweifel.dev]
– ashallendesign.co.uk - submitted by Ash Allen
Learn about how to use DynamoDB in Laravel for caching and storing Laravel models.
Read more [ashallendesign.co.uk]
– tighten.com - submitted by Jamison Valenta
When it comes to caching, we have to balance performance gains with increased cost of complexity and infrastructure. In our latest post, we talk through a few different caching strategies and approaches so you know the best caching tool for any situation.
Read more [tighten.com]
– rias.be
Stale While Revalidate (SWR) is a strategy to first return the data from the cache, then send the fetch request, and finally come up with the up-to-date data.
Read more [rias.be]
A typical Laravel application will likely have many routes, config files and possibly some events. In your development environment, these routes and config files will be loaded and registered in each request. The performance penalty for this is not too big. In a production environment, you want to…
Response caching is like a progressive enhancement. It will make your app faster in some ways, and some cases, but your app must work perfectly well without it.
Read more [samuelstancl.me]
I've just released a new major version of the spatie/once package. This version uses the WeakMap class which is introduced in PHP 8. In this short post I'd like explain why this change was made.
Larry Garlfriend explains how you can use PHP 8's weak maps to implement a self cleaning cache. Pretty sweet!
Read more [platform.sh]
When a request comes in your app will return a response. To create that response, your application has to do some work. Most likely queries will execute. This all takes some time. Wouldn't it be nice if the same request comes in, we can return the response the application has constructed previously?
On the Oh Dear! blog, Mattias Geniar explains how you can use our service to keep your Varnish cache warm.
Slow websites are annoying, right? We sure think so. One common solution is to introduce a caching proxy like Varnish to help cache pages and reduce your server load. The good news is, if you have Oh Dear!, you can let those 2 work together.
Read more [ohdear.app]
Misconceptions about HTTP caching for APIs abound. Here is a little thread that covers a bunch of them.
— Crashy McCiderface (@philsturgeon) October 10, 2018
1. "Caching API responses is WRONG, using caching for performance is a crutch and the endpoint should just be fast.
Read more [twitter.com]
Recently this button to optimize PHP's OPcache was added to Laravel Forge.
If you were wondering what PHP OPcache is all about and what pressing this button does with your application, read this article Olav van Schie wrote on the subject a while ago.
Every time you execute a PHP script, the script needs to be compiled to byte code. OPcache leverages a cache for this bytecode, so the next time the same script is requested, it doesn’t have to recompile it. This can save some precious execution time, and thus make your app faster (and maybe save some server costs).
https://medium.com/appstract/make-your-laravel-app-fly-with-php-opcache-9948db2a5f93
In a short blogpost Michael Dyrynda gives some good advice on why you should cache your routes and config values.
As part of the recommended production deploy process it is important to run the caching commands that Laravel affords us via Artisan. This means running config:cache and route:cache, which will compile the config and route files down into a single file each.In doing so, Laravel aims to speed up parsing of these files by only needing to read a single, rather than multiple files.
https://dyrynda.com.au/blog/environment-variables-config-caching-and-laravel
If you want to learn Varnish Thijs Feryn wrote a book for you. It's free to download until 7th March 2017.
Getting Strated with Varnish Cache is a technical book about the Varnish caching technology. Varnish is a so-called reverse caching proxy that acts as an intermediary between the browser and the webserver. Varnish stores HTTP responses and serves them to the browser, without accessing the backend for every request. This causes a massive speed increase.
For a project we're working on at Spatie we're expecting high traffic. That's why we spent some time researching how to improve the request speed of a Laravel application and the amount of requests a single server can handle. There are many strategies and services you can use to speed up a site. In…
Varnish is a piece of software that, amongst other things, can make your website much faster. In a new post on his blog, Mattias Geniar tells you all about it.
Varnish can do a lot of things, but it's mostly known as a reverse HTTP proxy. It brands itself as an HTTP accelerator, making HTTP requests faster by caching them. ... Varnish is usually associated with performance, but it greatly increases your options to scale your infrastructure (load balancing, failover backends etc) and adds a security layer right out of the box: you can easily let Varnish protect you from the httpoxy vulnerability or slowloris type attacks.
https://ma.ttias.be/varnish-explained/
Be sure to watch Mattias' excellent talk he gave at this years Laracon: