Docs Connect Components Caches 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: cache_resources: - label: foobar memcached: addresses: - localhost:11211 default_ttl: 60s It’s possible to layer caches with read-through and write-through behavior 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. Back to top × Simple online edits For simple changes, such as fixing a typo, you can edit the content directly on GitHub. Edit on GitHub Or, open an issue to let us know about something that you want us to change. Open an issue Contribution guide For extensive content updates, or if you prefer to work locally, read our contribution guide . Was this helpful? thumb_up thumb_down group Ask in the community mail Share your feedback group_add Make a contribution zmq4 aws_dynamodb