The feature I am looking at is what has already been described identically here https://blog.nginx.org/blog/benefits-of-microcaching-nginx
The only difference is that instead of looking at Apache/WordPress as slow and in need of speedup, you instead look at Node.js JavaScript invocation as slow and in need of speedup.
We both use the same very 1 second cache expiry, so it's obvious we already made the same conclusions.
I'm thinking the feature should be entirely backwards compatible and opt-in per route, and basically have (at least) 2 parameters: lower expiry and maximum expiry (I have already forgotten how I came to that idea but trust me I know it was smart).
Benchmarking already shows 10x performance over Fastify and you can apply this caching to a lot of routes (dynamic content, not personal).
It's the best thing since sliced bread. And it definitely will replace DeclarativeResponse. I love it.
Also, with a proper cache, it makes sense to maybe look at io_uring since you now actually have a need for better performance as you can escape the JS bottleneck!
The feature I am looking at is what has already been described identically here https://blog.nginx.org/blog/benefits-of-microcaching-nginx
The only difference is that instead of looking at Apache/WordPress as slow and in need of speedup, you instead look at Node.js JavaScript invocation as slow and in need of speedup.
We both use the same very 1 second cache expiry, so it's obvious we already made the same conclusions.
I'm thinking the feature should be entirely backwards compatible and opt-in per route, and basically have (at least) 2 parameters: lower expiry and maximum expiry (I have already forgotten how I came to that idea but trust me I know it was smart).
Benchmarking already shows 10x performance over Fastify and you can apply this caching to a lot of routes (dynamic content, not personal).
It's the best thing since sliced bread. And it definitely will replace DeclarativeResponse. I love it.
Also, with a proper cache, it makes sense to maybe look at io_uring since you now actually have a need for better performance as you can escape the JS bottleneck!