960ff8bd39 | ||
---|---|---|
.github | ||
doctests | ||
example | ||
extra | ||
fuzz | ||
internal | ||
scripts | ||
.gitignore | ||
.golangci.yml | ||
.prettierrc.yml | ||
CHANGELOG.md | ||
CONTRIBUTING.md | ||
LICENSE | ||
Makefile | ||
README.md | ||
RELEASING.md | ||
acl_commands.go | ||
bench_decode_test.go | ||
bench_test.go | ||
bitmap_commands.go | ||
bitmap_commands_test.go | ||
cluster_commands.go | ||
command.go | ||
command_test.go | ||
commands.go | ||
commands_test.go | ||
doc.go | ||
error.go | ||
example_instrumentation_test.go | ||
example_test.go | ||
export_test.go | ||
gears_commands.go | ||
gears_commands_test.go | ||
generic_commands.go | ||
geo_commands.go | ||
go.mod | ||
go.sum | ||
hash_commands.go | ||
hyperloglog_commands.go | ||
internal_test.go | ||
iterator.go | ||
iterator_test.go | ||
json.go | ||
json_test.go | ||
list_commands.go | ||
main_test.go | ||
monitor_test.go | ||
options.go | ||
options_test.go | ||
osscluster.go | ||
osscluster_commands.go | ||
osscluster_test.go | ||
pipeline.go | ||
pipeline_test.go | ||
pool_test.go | ||
probabilistic.go | ||
probabilistic_test.go | ||
pubsub.go | ||
pubsub_commands.go | ||
pubsub_test.go | ||
race_test.go | ||
redis.go | ||
redis_test.go | ||
result.go | ||
ring.go | ||
ring_test.go | ||
script.go | ||
scripting_commands.go | ||
search_commands.go | ||
search_test.go | ||
sentinel.go | ||
sentinel_test.go | ||
set_commands.go | ||
sortedset_commands.go | ||
stream_commands.go | ||
string_commands.go | ||
timeseries_commands.go | ||
timeseries_commands_test.go | ||
tx.go | ||
tx_test.go | ||
universal.go | ||
universal_test.go | ||
version.go |
README.md
Redis client for Go
go-redis is brought to you by ⭐ uptrace/uptrace. Uptrace is an open-source APM tool that supports distributed tracing, metrics, and logs. You can use it to monitor applications and set up automatic alerts to receive notifications via email, Slack, Telegram, and others.
See OpenTelemetry example which demonstrates how you can use Uptrace to monitor go-redis.
How do I Redis?
Learn for free at Redis University
Build faster with the Redis Launchpad
Documentation
Resources
Ecosystem
This client also works with Kvrocks, a distributed key value NoSQL database that uses RocksDB as storage engine and is compatible with Redis protocol.
Features
- Redis commands except QUIT and SYNC.
- Automatic connection pooling.
- Pub/Sub.
- Pipelines and transactions.
- Scripting.
- Redis Sentinel.
- Redis Cluster.
- Redis Ring.
- Redis Performance Monitoring.
- Redis Probabilistic [RedisStack]
Installation
go-redis supports 2 last Go versions and requires a Go version with modules support. So make sure to initialize a Go module:
go mod init github.com/my/repo
Then install go-redis/v9:
go get github.com/redis/go-redis/v9
Quickstart
import (
"context"
"fmt"
"github.com/redis/go-redis/v9"
)
var ctx = context.Background()
func ExampleClient() {
rdb := redis.NewClient(&redis.Options{
Addr: "localhost:6379",
Password: "", // no password set
DB: 0, // use default DB
})
err := rdb.Set(ctx, "key", "value", 0).Err()
if err != nil {
panic(err)
}
val, err := rdb.Get(ctx, "key").Result()
if err != nil {
panic(err)
}
fmt.Println("key", val)
val2, err := rdb.Get(ctx, "key2").Result()
if err == redis.Nil {
fmt.Println("key2 does not exist")
} else if err != nil {
panic(err)
} else {
fmt.Println("key2", val2)
}
// Output: key value
// key2 does not exist
}
The above can be modified to specify the version of the RESP protocol by adding the protocol
option to the Options
struct:
rdb := redis.NewClient(&redis.Options{
Addr: "localhost:6379",
Password: "", // no password set
DB: 0, // use default DB
Protocol: 3, // specify 2 for RESP 2 or 3 for RESP 3
})
Connecting via a redis url
go-redis also supports connecting via the redis uri specification. The example below demonstrates how the connection can easily be configured using a string, adhering to this specification.
import (
"github.com/redis/go-redis/v9"
)
func ExampleClient() *redis.Client {
url := "redis://user:password@localhost:6379/0?protocol=3"
opts, err := redis.ParseURL(url)
if err != nil {
panic(err)
}
return redis.NewClient(opts)
}
Advanced Configuration
go-redis supports extending the client identification phase to allow projects to send their own custom client identification.
Default Client Identification
By default, go-redis automatically sends the client library name and version during the connection process. This feature is available in redis-server as of version 7.2. As a result, the command is "fire and forget", meaning it should fail silently, in the case that the redis server does not support this feature.
Disabling Identity Verification
When connection identity verification is not required or needs to be explicitly disabled, a DisableIndentity
configuration option exists. In V10 of this library, DisableIndentity
will become DisableIdentity
in order to fix the associated typo.
To disable verification, set the DisableIndentity
option to true
in the Redis client options:
rdb := redis.NewClient(&redis.Options{
Addr: "localhost:6379",
Password: "",
DB: 0,
DisableIndentity: true, // Disable set-info on connect
})
Unstable RESP3 Structures for RediSearch Commands
When integrating Redis with application functionalities using RESP3, it's important to note that some response structures aren't final yet. This is especially true for more complex structures like search and query results. We recommend using RESP2 when using the search and query capabilities, but we plan to stabilize the RESP3-based API-s in the coming versions. You can find more guidance in the upcoming release notes.
Contributing
Please see out contributing guidelines to help us improve this library!
Look and feel
Some corner cases:
// SET key value EX 10 NX
set, err := rdb.SetNX(ctx, "key", "value", 10*time.Second).Result()
// SET key value keepttl NX
set, err := rdb.SetNX(ctx, "key", "value", redis.KeepTTL).Result()
// SORT list LIMIT 0 2 ASC
vals, err := rdb.Sort(ctx, "list", &redis.Sort{Offset: 0, Count: 2, Order: "ASC"}).Result()
// ZRANGEBYSCORE zset -inf +inf WITHSCORES LIMIT 0 2
vals, err := rdb.ZRangeByScoreWithScores(ctx, "zset", &redis.ZRangeBy{
Min: "-inf",
Max: "+inf",
Offset: 0,
Count: 2,
}).Result()
// ZINTERSTORE out 2 zset1 zset2 WEIGHTS 2 3 AGGREGATE SUM
vals, err := rdb.ZInterStore(ctx, "out", &redis.ZStore{
Keys: []string{"zset1", "zset2"},
Weights: []int64{2, 3}
}).Result()
// EVAL "return {KEYS[1],ARGV[1]}" 1 "key" "hello"
vals, err := rdb.Eval(ctx, "return {KEYS[1],ARGV[1]}", []string{"key"}, "hello").Result()
// custom command
res, err := rdb.Do(ctx, "set", "key", "value").Result()
Run the test
go-redis will start a redis-server and run the test cases.
The paths of redis-server bin file and redis config file are defined in main_test.go
:
var (
redisServerBin, _ = filepath.Abs(filepath.Join("testdata", "redis", "src", "redis-server"))
redisServerConf, _ = filepath.Abs(filepath.Join("testdata", "redis", "redis.conf"))
)
For local testing, you can change the variables to refer to your local files, or create a soft link
to the corresponding folder for redis-server and copy the config file to testdata/redis/
:
ln -s /usr/bin/redis-server ./go-redis/testdata/redis/src
cp ./go-redis/testdata/redis.conf ./go-redis/testdata/redis/
Lastly, run:
go test
Another option is to run your specific tests with an already running redis. The example below, tests against a redis running on port 9999.:
REDIS_PORT=9999 go test <your options>
See also
- Golang ORM for PostgreSQL, MySQL, MSSQL, and SQLite
- Golang PostgreSQL
- Golang HTTP router
- Golang ClickHouse ORM
Contributors
Thanks to all the people who already contributed!