You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As UI frameworks undulate back tot he server for rendering our Edge networks provide stellar performance. When building a Remix app, for example, it's possible to render pages entirely on edge and serve them closest to users. As apps grow in complexity and audience they will typically look towards implementing a caching strategy. Would node-lru-cache be ideal for such a situation? Has anyone tried running this package in an edge context to determine if the Node APIs used are supported in other runtimes? Are there any other packages you might recommend for edge-side caching with JavaScript?
The text was updated successfully, but these errors were encountered:
As UI frameworks undulate back tot he server for rendering our Edge networks provide stellar performance. When building a Remix app, for example, it's possible to render pages entirely on edge and serve them closest to users. As apps grow in complexity and audience they will typically look towards implementing a caching strategy. Would
node-lru-cachebe ideal for such a situation? Has anyone tried running this package in an edge context to determine if the Node APIs used are supported in other runtimes? Are there any other packages you might recommend for edge-side caching with JavaScript?The text was updated successfully, but these errors were encountered: