parse-community / parse-community/parse-server
Add the global redis cache the ability for caching query results
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest version of Parse Server.
Issue Description
It would be nice to have global redis cache cache query results from Mongo DB by default.
Steps to reproduce
- Install a redis server and make sure it's running.
- Connect the redis server to parse via redis adapter like this:
const RedisCacheAdapter = require("parse-server").RedisCacheAdapter;
const serverConfig = {
...
cacheAdapter: new RedisCacheAdapter({ url: process.env.REDIS_URL }),
...
}
Environment
node 18.2.0
redis-server on local docker v7.0.10
redis-server on digital ocean droplet with ubuntu 22 v7.0.4
Server
- Parse Server version:
^6.0.0 - Operating system:
Win 64 - Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc):
Redis server tested both on redis-server version=7.0.10 on a local docker container as well as digital ocean droplet with ubuntu 22 redis-version 7.0.4
Database
- System (MongoDB or Postgres):
Mongo - Database version:
5.0.15 - Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc):
Atlas
Client
- SDK (iOS, Android, JavaScript, PHP, Unity, etc):
JavaScript - SDK version:
^4.0.1
Logs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how serverConfig wires RedisCacheAdapter into Parse Server and how MongoDB query results are currently handled. The issue names no files or tests, so first identify the cache integration and query paths; done would mean defining and verifying the requested default Redis caching behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, mongodb, node.js, redis
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100