Should I reuse the connection on Redis or close it after every use?

This page summarizes the projects mentioned and recommended in the original post on /r/golang

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • Asynq

    Simple, reliable, and efficient distributed task queue in Go

  • I just need to ask a question, it's my first time using go, and have been working on a little project of mine that uses: https://github.com/hibiken/asynq

  • Redis

    Redis Go client

  • Asynq uses https://github.com/go-redis/redis in order to connect to Redis. Whenever you create a client using go-redis, the client internally manages a connection pool, so when you need to execute a command in Redis the client just retrieves a connection from the pool and uses it. After using it, the connection is released and it goes back to the pool (no need to say that the Redis client is thread-safe).

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts