Use Redis (or alternative) for session store instead of MongoDB
See original GitHub issueI was checking the telemetry on the ops dashboard, and by far freecodecamp.sessions.find
is the most (expected) used query.
We maybe able optimize the load by using a Redis session store instead of MongoDB?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:8 (8 by maintainers)
Top Results From Across the Web
MongoDB Vs. Redis Comparison: Pros And Cons
Redis is an in-memory data store, while MongoDB's default storage engine, WiredTiger, stores data on disk.
Read more >MongoDB vs Redis for user sessions? - node.js - Stack Overflow
Currently, I query mongodb and store those fields in redis alongside any particular state information in a single hash that is keyed by...
Read more >Redis vs MongoDB: Which One Should You Choose in 2022?
Redis stores data in-memory using various key values. It excels over MongoDB when working with rapidly changing data, but because most of that ......
Read more >MongoDB vs. Redis — Which Database Should You Use?
Speed: Redis is faster than MongoDB because it's an in-memory database. ; RAM: Redis uses more RAM than MongoDB for non-trivial data sets....
Read more >Comparing In Memory Databases: Redis Vs. MongoDB
Performance · Redis performs considerably better for reads for all sorts of workloads, and better for writes as the workloads increase. · Even ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I am also in favor of moving some things over to Redis. @BerkeleyTrue and I have discussed this for at least a year. One other thing we’ve considered storing in Redis is campers’ solutions. This is how JSBin handles it.
This is something we can consider after we ship beta and our other mission-critical features.
I’m closing this issue as stale since it hasn’t been active lately. If you think this is still relevant to the newly updated platform, please explain why, then reopen it.