Cache Integration

[pdrivom]

Is your feature request related to a problem? Please describe.
For larger applications with a lot of data, caching architecture can increase greatly the performance of retrieving data.

Describe the solution you'd like
On the database query layer, first check if data exists on Redis, otherwise get on Postgres.

[seapagan]

Hi @pdrivom

Yeah, this is a good idea. I'll look at adding this when I've completed the base functionality of the template.

EDIT:
A plugin exists to do this fastapi-redis-cache so it should be reasonably straightforward. I'll look at it later. Getting my solar panels wired in today though so my 'leccy may be on and off.

[pdrivom]

Hey @seapagan, yes, should be a kinda "easy" feature to add.

Good luck with your solar panels. I'm an Electric and Computers Engineer, so I can relate how personal can get wiring tasks around the house 😃

[seapagan]

Hey @seapagan, yes, should be a kinda "easy" feature to add.

Hopefully. I've looked at the repo for that and there are a fair number of unmerged PRs to fix issues. I may end up forking that and merging them myself.

Good luck with your solar panels. I'm an Electric and Computers Engineer, so I can relate how personal can get wiring tasks around the house

Ta 😃. Sparky can't come today with the Battery sadly so it's postponed.

[seapagan]

This may get implemented earlier than planned since most of my ideas to implement rate-limiting and blocking use Redis anyway 😁. I may get this done over the weekend.

[seapagan]

Update:

I'm working on fixing and improving the fastapi-redis-cache package, which seems to have been abandoned. It has a few issues and false assumptions. There is also no way to easily expire a cache if new data is posted. Once I sort that, I'll add it to this package for caching

I prefer this package as it has a very easy caching mechanism using route decorators.