23

When you work with Redis after working on MongoDB... XD

Comments
  • 1
    Mongo is a lot more complicated, Redis is key/value only.
  • 1
    Yeh!! I use MongoDB throughout my application, but the homepage was so slow. So I used Redis for all data on my homepage. It was blazing fast! :D
  • 1
    Is that why Redis is a memory hog? I constantly get memory alerts for customers running Redis.
  • 1
    @Geezus Yep!! and that's why you have to use MongoDB; for large chunks of data!!
  • 1
    @Geezus good to know. It's even worse when they run Redis and SQL on the same sever. The stuff of nightmares......
  • 0
    @Geezus XD true that!!!
  • 1
    @Geezus what's the problem with using SQL as primary DB and reddis for caching data in the same app?
    This makes a perfext sense to me.
  • 0
    Redis is a in memory database, it is good for simple key/values on small data and caching but would never use it as it us being done here.
  • 0
    @nblackburn how is it being done here?
  • 0
    @ahmednr123 using reddis as primary data storage, instead of mongodb?
  • 0
    @hiestaa no... I wud never replace MongoDB with Redis... I want my home page to be fast and it doesn't really have much data on it! Just a 100 IDs and image URLs! Redis wud work perfectly fine!
  • 0
    @ahmednr123 indeed that's exactly what it's been designed for!
  • 1
    @hiestaa they're both RAM hogs. SQL will purposely chew up as much RAM as it can grab. Which makes sense and is fine if you have a lot of RAM but we have a lot of customers that do this on 1x1 or 1x2 boxes and have the memory alert threshold set to 90 or 95% so it causes constant headaches. I've even seen people run their Web sever, Apache, nine, etc, on the same server, we call them one hit wonders and they're awful.
  • 1
    @Geezus good to know!
Add Comment