Hi @brianleejackson,
Thanks for your reply. ?? That is really a great thing about APO. I will definitely check out the article link you have shared. But if you take out the fact that the Cache gets pushed to all the edges at the same time, I think our plugin will beat APO hands down at any time, due to optimizations, features and support to a whole lot of third party plugins and hostings.
I’m not sure if we can do something similar with our plugin as our architecture is different and flexible. But I will definitely brainstorm on this matter. I personally think they reason CF APO is able to do this is that they hold the HTML of a page in the KV which gets install populated all around the world and then when a new user visits a page the worker might be checking something like if the cache is not present in CF then pull it from the KV which is already present at that edge. I’m not 100% sure as CF will not share their code with me, but from my experience, I think the logic is something like that.
Personally, I don’t use APO on any of my client sites despite they have CF Pro plan just because this plugin gives so much flexibility and features over what CF APO provides, not to mention, here anyone can overwrite the official worker code added by us (if worker mode is selected) and then sprinkle in their own logics and requirements onto that (which is the case for a few of my client sites).
But I would love to know your opinion on the matter, especially the strength of APO over this plugin (except the feature of pushing cache across the whole world feature). Is there any sites or use cases where you felt using this plugin like I wish I should use the APO instead.
Love to hear your feedbacks. ??