-
Notifications
You must be signed in to change notification settings - Fork 456
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🚀 Feature: Implement Redis Caching for Job Listings to Improve Load Times #559
Comments
@VineeTagarwaL-code should we implement this?? |
Hey @Paribesh01 ! I have some experience with Redis, can I help contribute to this as well Thank you! |
yeah sounds like a good thing to work on, will be easy to implement and stuff just have to think about revalidation and stuff when new job gets added will ask bhayiya about this and get back to you |
@VineeTagarwaL-code what's the update should I start working?? |
good thinking indeed, but i want something else we are not using tanstack query for job fetching and stuff, can you migrate our current fetching to tanstack query, it has inbuilt caching and global state solution do it only for jobs now, no need to stress about the whole codebase |
@VineeTagarwaL-code ok, i will start working.. |
Hey @Paribesh01 , i can help on this as well if you want me to Thank you! |
🔖 Feature description
The caching feature aims to improve the performance and responsiveness of the job board application by temporarily storing frequently accessed job listings, search results, and filter queries in a caching layer (using Redis).
🎤 Why is this feature needed ?
Implementing a caching feature in the job board application is crucial for enhancing performance and improving user experience by reducing load times for frequently accessed data.
✌️ How do you aim to achieve this?
we will start by setting up a Redis server for storing cached data. We'll adjust how we fetch job listings so that the application first checks the cache for data before going to the database. This will involve creating unique keys for the cached data based on different job filters. We’ll also implement rules for how long data stays in the cache and when it should be removed to ensure users always see up-to-date information.
🔄️ Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: