We could use redis in the bot for caching the api results and potentially various other things. However, integrating redis would mean everyone would need to have a redis instance available to be used when developing, or be forced to use docker. This may be a bit too complex for the contributors.
To avoid this complexity, @Paillat-dev has suggested using https://github.com/aio-libs/aiocache, which can just store the records into memory on it's own, without redis running on the side. This does indeed look very interesting, as it allows us to still have a cache service without the complexities involved with setting it up as a service running externally.
The aiocache library also supports actual redis integration, so it would even allows us to switch to redis eventually, if we would want it.
Unless it's deemed that cache really is needed though, we don't necessarily have to do anything.
We could use redis in the bot for caching the api results and potentially various other things. However, integrating redis would mean everyone would need to have a redis instance available to be used when developing, or be forced to use docker. This may be a bit too complex for the contributors.
To avoid this complexity, @Paillat-dev has suggested using https://github.com/aio-libs/aiocache, which can just store the records into memory on it's own, without redis running on the side. This does indeed look very interesting, as it allows us to still have a cache service without the complexities involved with setting it up as a service running externally.
The aiocache library also supports actual redis integration, so it would even allows us to switch to redis eventually, if we would want it.
Unless it's deemed that cache really is needed though, we don't necessarily have to do anything.