Welcome to OGeek Q&A Community for programmer and developer-Open, Learning and Share
Welcome To Ask or Share your Answers For Others

Categories

0 votes
568 views
in Technique[技术] by (71.8m points)

node.js - How to namespace keys on redis to avoid name collisions?

I want to use redis to store some of my own key-value pairs, however some of my modules already use it. The redis express session store for session data, as well as the redis adapter for socket io. So my question is simple, how can I create or designate a database/namespace to store my own keys without key collisions? I am using the node-redis driver.

See Question&Answers more detail:os

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome To Ask or Share your Answers For Others

1 Reply

0 votes
by (71.8m points)

Solution 1: Store data of different modules in different Redis instances

The most strictly isolation is storing data of each module in an individual Redis instance, i.e. an individual Redis process.

Solution 2: Store data of different modules in different databases of a single Redis instance

A Redis instance can have multiple databases, and you can configure the number of databases in the config file. By default, there are 16 databases.

These databases are named with a zero-based numeric index. With the select command, you can use the ith database. After the selection, any subsequent commands will operate on the ith database.

So, if you assign an independent database for each module, you can avoid name collisions.

NOTE: this solution DOES NOT work with Redis Cluster. Redis Cluster only allows you to use the 0th database.

Solution 3: Create namespace with key prefix

If all of your data has to be stored in a single database, you can still implicitly create a namespace with key prefix. For each module, all data of this module should have the same key pattern: ModuleName:KeyName, i.e. each key of this module has the same prefix: ModuleName.

Since each module has a different name, there won't be any name collisions among these modules:

// Set keys for module1
SET module1:key1 value
SET module1:key2 value

// Set keys for module2
SET module2:key1 value
SET module2:key2 value

NOTE: this solution also works with Redis Cluster.


与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
OGeek|极客中国-欢迎来到极客的世界,一个免费开放的程序员编程交流平台!开放,进步,分享!让技术改变生活,让极客改变未来! Welcome to OGeek Q&A Community for programmer and developer-Open, Learning and Share
Click Here to Ask a Question

...