[ad_1]
I am becoming delusional with WordPress lately, for most sites that are very basic and static, you can use optimizations, but for the things that actually require you to use optimizations, larger solutions, more advanced functionality.
I am coming to discover that most of the time, you can’t.
Am I understanding this wrong ? why would have high volume solutions, when you can’t leverage caching ?
Help me understand what I am missing to see here ?
What exactly are you trying to say?
There are multiple types of caching: page caching, edge caching, caching of AJAX things like FacetWP, object caching (Redis), Memcached, and there is also stuff like Varnish.
Different use cases require different cache types. If the page content changes frequently or requires constant data transfer from the database, page caching may not work.
So the first thing to lay out here: caching is hard.
In WordPress, what a lot of people refer to when they talk about caching are caching plugins. These are “out of the box” solutions that do a generic set of things that work for “most people”
The moment you move to any type of advanced functionality, you’ll find that the “out of the box” solutions don’t really cover your use case anymore. That’s not to say they are bad solutions, they just aren’t made to cover every edge case.
You can always write your own caching optimizations as well. Often times as a site becomes more complex this is generally the only option you’ll have.
I recently wrote a WordPress site that needed to fetch large chunks of data from an external service and then render it in various parts of the site. We still used an “out of the box” cache plug-in, but had to turn most of it off and only let it cache specific sections. The actual data from the external service was cached by my own script that ran on a cron job to have a smaller impact to users.
> I am coming to discover that most of the time, you can’t.
100% caching works and can still be used in significantly more complex situations. At that point, you just need knowledge and experience, and you can’t just install a random plugin from a random dev and expect everything to go well.
On our websites, there are 3 or 4 layers of caching (each their own specialty / for their own reasons), some distributed across multiple nodes to serve people locally, that work perfectly.
You can use rocket.net. They say you don’t need to use a cache plugin except for optimization.
I tested a site with a good amount of traffic without a cache and it was doing well.
Just an idea