我正在尝试设计一个无状态且可扩展的 Web 系统。对于“会话”概念,我正在考虑使用 Redis 作为会话仓库。
但是您认为使用 NoSQL 系统是否适合该目的?是不是矫枉过正?我是否应该考虑另一个 NoSQL 系统(我当然不是在寻找购物清单。我的意思是另一个比 Redis 更适合存储会话数据的 NoSQL)?
我正在尝试设计一个无状态且可扩展的 Web 系统。对于“会话”概念,我正在考虑使用 Redis 作为会话仓库。
但是您认为使用 NoSQL 系统是否适合该目的?是不是矫枉过正?我是否应该考虑另一个 NoSQL 系统(我当然不是在寻找购物清单。我的意思是另一个比 Redis 更适合存储会话数据的 NoSQL)?
But do you think using a NoSQL system is suitable for that purpose?
Yes, NoSQL systems are suitable for this use case, namely K/V stores like redis if your session data are not too complex.
Is it an overkill?
No, it's a right tool for the right job. Redis is used in many scenarios and session store is one where it excells thanks to it's speed and support for advanced data structures which might come handy for you.
Should I consider another NoSQL?
There are other NoSQL solutions which might be used as a session store, for example riak or couchbase, but which one you choose depends on how complex your data are and also other factors like scalability and durability requirements.