Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/jgaskins/redis

Pure-Crystal Redis client, supporting clustering, RedisJSON, RediSearch, RedisGraph, and RedisTimeSeries
https://github.com/jgaskins/redis

crystal crystal-lang redis redis-client redis-cluster redis-graph redis-json redis-timeseries redisearch redisjson redistimeseries

Last synced: 14 days ago
JSON representation

Pure-Crystal Redis client, supporting clustering, RedisJSON, RediSearch, RedisGraph, and RedisTimeSeries

Awesome Lists containing this project

README 

        
# redis



A pure-Crystal implementation of the Redis protocol



## Installation



1. Add the dependency to your `shard.yml`:



   ```yaml

   dependencies:

     redis:

       github: jgaskins/redis

   ```



2. Run `shards`



## Usage



```crystal

require "redis"



redis = Redis::Client.new # Defaults to `localhost` port 6379



redis.set "foo", "bar"

redis.get "foo" # => "bar"



redis.incr "counter" # => 1

redis.incr "counter" # => 2

redis.decr "counter" # => 1



redis.del "foo", "counter" # => 2

```



### Pipelined queries



To mitigate latency with multiple queries whose inputs and outputs are completely independent of each other, you can "pipeline" your queries by sending them all at once before reading them. To do this, you can use the `pipeline` method:



```crystal

redis.pipeline do |pipe|

  pipe.incr "foo"

  pipe.set "bar", "baz"

  pipe.lpush "my-list", "my value"

end

```



The return value of `pipeline` will be an array containing the values of each of those calls in the order they were sent. So in this case, it might be `[1, nil, 2]` to match the return values of `incr`, `set`, and `lpush`, respectively.



### Transactions



The Redis [`MULTI` command](https://redis.io/commands/multi) begins a transaction, so you can use the `multi` method to execute a transaction against the server:



```crystal

redis.multi do |txn|

  txn.set "foo", "bar"

  txn.incr "baz"

  txn.lpush "my-list", "my value"

end

```



The transaction is automatically committed with [`EXEC`](https://redis.io/commands/exec) at the end of the block. If an exception occurs within the block, the transaction will be rolled back with [`DISCARD`](https://redis.io/commands/discard) before exiting the block.



You may also call `txn.discard`, which will effectively disable the transaction (all further methods called on the transaction do nothing), but will not exit the block. You will need to exit the block explicitly with `break` if there are operations within the block that cannot be rolled back, such as sending an email or sending a request to a third-party API.



The reason for this is that the only way to exit a containing block from an inner method in Crystal is to raise an exception, and this library chooses not to use exceptions for flow control.



### Beyond `localhost`



To use a Redis server that isn't at `localhost:6379`, pass a `URI` to the client. For example, if you store it in your shell environment:



```crystal

redis = Redis::Client.new(URI.parse(ENV["REDIS_URL"]))



# ... or ...



redis = Redis::Client.from_env("REDIS_URL")

```



To connect via SSL, make sure you use the `rediss://` URL scheme. If your Redis server requires a password or uses a different database slot than `0`, make sure you include them in the URL:



```crystal

redis = Redis::Client.new(URI.parse("rediss://:[email protected]/3"))

```



### Connection Pool



The `Redis::Client` maintains a connection pool, so there is no need to run your own within your application. When you execute a command on the `Redis::Client`, it is automatically executed against a connection. When you execute a pipeline or transaction with `multi`, all commands within that block will automatically be routed to the same connection.



**Configuration**



For this shard, we use the following default setting (outside of the Standard Lib defaults);



```

max_idle_pool_size = 25

```



> You can override this manually using the URI parameters.

> All other settings follow the DB::Pool defaults.



The behaviour of the connection pool can be configured from a set of query string parameters in the connection URI.



| Name | Default value |

| :--- | :--- |

| initial\_pool\_size | 1 |

| max\_pool\_size | 0 \(unlimited\) |

| max\_idle\_pool\_size | 1 |

| checkout\_timeout | 5.0 \(seconds\) |

| retry\_attempts | 1 |

| retry\_delay | 1.0 \(seconds\) |



See [Crystal guides](https://crystal-lang.org/reference/1.6/database/connection_pool.html) to learn more.



**Example**



```crystal

pool_params = "?initial_pool_size=1&max_pool_size=10&checkout_timeout=10&retry_attempts=2&retry_delay=0.5&max_idle_pool_size=50"

redis = Redis::Client.new(URI.parse("redis://localhost:6379/0#{pool_params}"))

```



**Recommendations**



If you encounter any issues, keep these setting the same;



- `initial_pool_size`

- `max_pool_size`

- `max_idle_pool_size`



Example:



```

initial_pool_size = 50

max_pool_size = 50

max_idle_pool_size = 50

```



### TCP Keep-Alive



The `Redis::Client` uses a pool of `Redis::Connection` under the hood.

Within `Redis::Connection` we create a `TCPSocket`, which can accept keepalive params.

The TCP keepalive settings can help you mitigate Redis connection stability issues.



> NOTE: This behaviour is disabled by default. See Configuration below on how to enable it.



**Configuration**



For this shard, we use the following override setting;



| Name | Default value |

| :--- | :--- |

| keepalive | false |

| keepalive\_count | 3 |

| keepalive\_idle | 60 |

| keepalive\_interval | 30 |



> You can override this manually using the URI parameters.

> The settings above have proven to have good results in production environments. However, every environment is different, so tweaking these settings may be necessary.



See [Crystal API](https://crystal-lang.org/api/1.6.0/TCPSocket.html) to learn more.



**Example**



```crystal

params = "?keepalive=true&keepalive_count=5&keepalive_idle=10&keepalive_interval=15"



redis = Redis::Client.new(URI.parse("redis://localhost:6379/0#{params}"))

# or direct connections

redis = Redis::Connection.new(URI.parse("redis://localhost:6379/0#{params}"))

```



**Recommendations**



Enable this setting with the defaults if you are encountering connection issues.



Example:



```crystal

params = "?keepalive=true"



redis = Redis::Client.new(URI.parse("redis://localhost:6379/0#{params}"))

# or direct connections

redis = Redis::Connection.new(URI.parse("redis://localhost:6379/0#{params}"))

```



## Development



Make sure you have a Redis or KeyDB server running locally on port 6379.



Redis must be installed with a stack server for the full text search (`ft`) and time series modules (`ts`) in order for all specs to run.



### With Docker



You can use this for your docker-compose file



```yaml

redis:

  image: redis/redis-stack-server

  ports:

    - "6379:6379"

```



### With Homebrew



Install the [`redis-stack` from homebrew](https://github.com/redis-stack/homebrew-redis-stack)



## Contributing



1. Fork it ()

2. Create your feature branch (`git checkout -b my-new-feature`)

3. Commit your changes (`git commit -am 'Add some feature'`)

4. Push to the branch (`git push origin my-new-feature`)

5. Create a new Pull Request



## Contributors



- [Jamie Gaskins](https://github.com/jgaskins) - creator and maintainer