python-betterproto VS aioredis

For context: in a project I was working on recently, we relied heavily on Protocol buffers. All our internal and external services expose a GRPC interface. Also the client libraries that are used by the end users rely on the Proto service interfaces. However, shipping simply the generated code that comes with the official protoc Python plugin or any other standardised Python protoc plugin (like betterproto) was not sufficient for us. We wanted certain modifications and additions to the generated client code like service clients that would automatically pick up credentials/service account files, a more Pythonic handling for requests that work with pagination or long running operations etc.

First, it was aioredis library. We are using sentinel based client because with this we can achieve failover easily. Aioredis spawn pool of connections, that transparently reconnects (and here third thing — FOREVER, hello DDOS) to our sentinel nodes, and then to master node. It supposed to do so. Also, we found that if you are not limiting maximum connections count, library will do it for you and set it as 2 ** 31 (here you can see it) — this is fourth thing. Furthermore, pool in our version (2.0.1) not closing automatically, and it makes the problem worse.

I'm hoping to leverage Redis with my project, and I was curious as to if anyone had any general pointers as to how best to manage the DB connection. I'm using aioredis such that I can leverage the async functionality, but I haven't been very happy with the library's documentation surrounding how best to leverage the connection pool. Most of the examples create and tear down the pool immediately without showing how best to manage its lifespan.