Cache Middleware added to caracal.js #174
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…the app from the server-side
|
Hello @birm , I have added a middleware for caching via the server-side rendering, I proceed to use Redis or service workers for the client-side caching. Let me know what you think about that, thanks. |
gbengaoluwadahunsi
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
I have implemented a new middleware in the application to enhance the server-side caching mechanism. This middleware will optimize response times and reduce server load by caching frequently accessed data.
Motivation
The motivation behind this enhancement is to improve the overall performance and scalability of the application. By implementing server-side caching, we aim to reduce the response time for requests, enhance the user experience, and minimize server resource utilization.
Testing
The new middleware has been thoroughly tested in various scenarios to ensure its effectiveness and compatibility with the existing application architecture. Testing involved simulating different load conditions and monitoring the caching behavior to validate its performance benefits.