1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
|
Caching
=======
Caching responses
------------------
Sometimes it's desirable to cache some responses, especially if these involve expensive calculations, or when polling is
expected. Litestar comes with a simple mechanism for caching:
.. literalinclude:: /examples/caching/cache.py
:language: python
:lines: 1, 4-8
By setting :paramref:`~litestar.handlers.HTTPRouteHandler.cache` to ``True``, the response from the handler
will be cached. If no ``cache_key_builder`` is set in the route handler, caching for the route handler will be
enabled for the :attr:`~.config.response_cache.ResponseCacheConfig.default_expiration`.
.. note:: If the default :paramref:`~litestar.config.response_cache.ResponseCacheConfig.default_expiration` is set to
``None``, setting up the route handler with :paramref:`~litestar.handlers.HTTPRouteHandler.cache` set to ``True``
will keep the response in cache indefinitely.
Alternatively you can specify the number of seconds to cache the responses from the given handler like so:
.. literalinclude:: /examples/caching/cache.py
:language: python
:caption: Caching the response for 120 seconds by setting the :paramref:`~litestar.handlers.HTTPRouteHandler.cache`
parameter to the number of seconds to cache the response.
:lines: 1, 9-13
:emphasize-lines: 4
If you want the response to be cached indefinitely, you can pass the :class:`~.config.response_cache.CACHE_FOREVER`
sentinel instead:
.. literalinclude:: /examples/caching/cache.py
:language: python
:caption: Caching the response indefinitely by setting the :paramref:`~litestar.handlers.HTTPRouteHandler.cache`
parameter to :class:`~litestar.config.response_cache.CACHE_FOREVER`.
:lines: 1-3, 14-18
:emphasize-lines: 5
Configuration
-------------
You can configure caching behaviour on the application level by passing an instance of
:class:`~.config.response_cache.ResponseCacheConfig` to the :class:`Litestar instance <.app.Litestar>`.
Changing where data is stored
+++++++++++++++++++++++++++++
By default, caching will use the :class:`~.stores.memory.MemoryStore`, but it can be configured with
any :class:`~.stores.base.Store`, for example :class:`~.stores.redis.RedisStore`:
.. literalinclude:: /examples/caching/redis_store.py
:language: python
:caption: Using Redis as the cache store.
Specifying a cache key builder
++++++++++++++++++++++++++++++
Litestar uses the request's path + sorted query parameters as the cache key. This can be adjusted by providing a
"key builder" function, either at application or route handler level.
.. literalinclude:: /examples/caching/key_builder.py
:language: python
:caption: Using a custom cache key builder.
.. literalinclude:: /examples/caching/key_builder_for_route_handler.py
:language: python
:caption: Using a custom cache key builder for a specific route handler.
Using the cache_response_filter
+++++++++++++++++++++++++++++++
The :attr:`~.config.response_cache.ResponseCacheConfig.cache_response_filter` can be customized to implement any caching logic based on the application's needs.
For example, you might want to cache only successful responses, or cache responses based on certain headers or content.
.. literalinclude:: /examples/caching/cache_response_filter.py
:language: python
:caption: Using the cache_response_filter to customize caching behavior.
In this example, the `custom_cache_response_filter` function caches only successful (2xx) responses.
|
