Comprehensive Guide to Listing Redis Databases

Overview of Redis Database Architecture

Redis, as a high-performance key-value store, employs a multi-database architecture design. Unlike relational databases, the number of databases in Redis is predefined in the configuration file, typically providing 16 databases by default, each identified by a numerical index. This design enables logical data isolation within a single instance while maintaining high-performance data access capabilities.

Retrieving Database Configuration Information

To determine the total number of databases in a Redis instance, the most straightforward approach is to query the runtime configuration. The CONFIG GET databases command retrieves the currently configured database count:

redis-cli CONFIG GET databases
1) "databases"
2) "16"

This command returns an array containing two elements: the first being the configuration item name "databases", and the second being the specific numerical value. In practical applications, this value corresponds to the maximum database index range supported by the Redis instance (from 0 to n-1).

Viewing Databases Containing Data

Although Redis configures multiple databases, only some may contain actual data during usage. The INFO keyspace command provides statistical information about databases that contain keys:

redis-cli INFO keyspace
# Keyspace
db0:keys=10,expires=0
db1:keys=1,expires=0
db3:keys=1,expires=0

The output displays detailed information for each database containing keys:

• dbX: Database identifier, where X is the database number
• keys: Number of keys in the current database
• expires: Number of keys with expiration time set

This method is particularly useful for monitoring and debugging scenarios, enabling quick assessment of database usage patterns.

Using Redis Serialization Protocol (RESP)

For applications requiring low-level communication, direct interaction with the Redis server can be achieved through the Redis Serialization Protocol (RESP). When using telnet connections, commands must be sent in RESP format:

telnet 127.0.0.1 6379
*2
$4
INFO
$8
keyspace

The RESP protocol employs a specific format:

• *n indicates an array containing n elements
• $m indicates the subsequent string has a length of m bytes
• Commands and parameters are treated as separate string elements

Server responses also follow the RESP format, returning strings containing statistical information.

Database Configuration in Configuration File

The number of databases in Redis is defined in the redis.conf configuration file through the databases parameter:

# redis.conf
databases 16

Modifying this configuration requires restarting the Redis service to take effect. Increasing the number of databases increases Redis memory overhead, as each database maintains independent data structures.

Practical Command Combinations

In operational environments, command combinations can quickly retrieve database information:

# Get information for all databases containing keys
redis-cli INFO | grep ^db

# Simultaneously retrieve configuration and usage information
redis-cli CONFIG GET databases && redis-cli INFO keyspace

These command combinations can be integrated into monitoring scripts for automated Redis database status monitoring.

Performance Considerations and Best Practices

When using multiple databases, consider the following:

• Database switching is achieved through the SELECT command, and frequent switching may impact performance
• Recommend storing related data in the same database to reduce switching overhead
• Regularly monitor database usage patterns using INFO keyspace
• For production environments, configure the database count appropriately based on actual requirements

Conclusion

Redis provides multiple methods for querying database information, each suited for different scenarios. CONFIG GET databases is ideal for retrieving configuration information, INFO keyspace for monitoring actual usage patterns, and the RESP protocol for low-level application development. Understanding the principles and appropriate use cases for these methods facilitates better management and optimization of Redis database usage.