Caches¶
A cache is a key/value store which can be used by certain components for applications such as deduplication or data joins. Caches are configured as a named resource:
It's possible to layer caches with read-through and write-through behaviour using the multilevel cache.
And then any components that use caches have a field resource
that specifies the cache resource:
pipeline:
processors:
- cache:
resource: foobar
operator: add
key: '${! json("message.id") }'
value: "storeme"
- mapping: root = if errored() { deleted() }
For the simple case where you wish to store messages in a cache as an output destination for your pipeline, check out the cache
output. To see examples of more advanced uses of caches such as hydration and deduplication, check out the cache
processor.
You can find out more about resources in this document.
Name | Tags |
---|---|
aws_dyanamodb | AWS |
aws_s3 | AWS |
couchbase | Couchbase |
file | Local |
gcp_cloud_storage | GCP |
memcached | Memcached |
memory | Memory |
mongodb | MongoDB |
multilevel | Multiple Cache Level |
redis | Redis |
ristretto | Ristretto |