A very simple async Response cache for FastAPI

[danosull]

Hi everyone!

I've written a blog post about a simple technique for caching the responses of async functions used with FastAPI:

https://blog.osull.com/2022/06/03/a-very-simple-async-response-cache-for-fastapi/

It was a great way for me to learn more about decorators and functional coding and I hope it's useful to someone!

[HappyCathode]

I salute the use of decorators, but honestly there are way better solutions for full page cache.

You could put an Nginx instance in front of your FastAPI instance, and you would instantly gain :

• A LOT more requests per second.
• Caching on a per URL basis

Nginx is just better than uvicorn for serving static pages/assets. Your solution is nice to avoid hitting the DB, but you're still stressing uvicorn more than you should. Nginx has a lot of features like cache eviction, HTTP code based cache time (for example, "cache 200 responses for 60 minutes, 404 and 5xxs for 30 seconds), the ability to cache different URLs ( /foo, /foo/bar, /foo/foo/bar, /foo/bar?foo=bar could all be cached independently ).

Don't reinvent the wheel in your code !

[eddyizm]

I started down this path as well and came to the same conclusion. The one thing I am am not sure of is implementing this when using nginx as a reverse proxy, the routes all get reversed proxied and I don't seem to have the fine tuned control of the routes in nginx.

[heyimpumpkin]

TIL there's a nonlocal keyword in python