Superfast, real-time page caching with push control. noDelay puts your application in control of its content. The cache reload is defined by the application not by the TTL.
It is a caching server, similar to varnish.
Using the noDelay API your application pushes content up to the cache ensuring your content is always available from cache to your end-users, no more waiting for TTLs to expire or slow page loads for the first user. Reach more people with less resources, noDelay reduces the server requests to the absolute minimum.
expressjs, async, underscore
Voting is now closed.
We have tried to provide a proof of concept here. There are a lot of compromises here in this build.
Whenever there is a change in content in WP, like adding a post, modifying a post, adding a comment etc, the Plugin in the wordpress calls the noDelay API, and asks noDelay to refresh the particular resources. In the current wordpress plugin, it just does so when you add/edit a post. Also the wordpress plugin just asks noDelay to reload the post page and the categories page.
The cached items in noDelay will not have a lifetime. Once cache it will be there for ever, unless the application asks it to reload. This can be related to something like a static web server. However the static content can be replaced by any backend application through the API.
I am not very sure, how this could work with cluster of distributed servers. I think the major advantage a caching server like Varnish gets by multiple backends is redundancy. But in this case, the cache does not contact the application server at all unless the application asks it to do so. So I am not sure of the need for redundancy.
Also, we wanted to work on optimizing the cached resources similar to google pagespeed. However we were not able to do that in 48 hours.
Thanks for your vote and comment.
Industrial Web Apps