Data caching overview

Introduction

A global cache is a repository for data that you want to reuse. For example, you can use a global cache in IBM MQ message flows to store correlation information for use beyond a specific message flow node, instance of a message flow, or integration server. The cache facilitates the sharing of data within an integration server and between integration servers, and eliminates the need for an alternative solution, such as a database. You can use one message flow node to store data in the global cache, then a second node (in the same message flow or a separate flow), can retrieve that data from the global cache.

You can use a message flow node to interact with the global cache. Interactions with the cache happen outside the message flow transaction, and are committed immediately. If an exception is thrown downstream of the node that interacts with the cache, the cache interactions are not rolled back.

Scenarios and tutorials

Choosing the right type of cache

You can choose between local cache, embedded global cache, external Redis global cache, embedded WebSphere® eXtreme Scale (WXS) grid, external WebSphere eXtreme Scale grid, or other caching types such as environment tree and long-lived variables based on your requirement. For more information about choosing the right type of cache, see Choosing the right type of cache.

Interaction with the global cache or external grid

You can interact with the global cache or external grid by using a Mapping node or a JavaCompute node. The node can put data into a map, retrieve data, and create a map if one does not exist. For more information, see Accessing the global cache by using a Mapping node or Accessing the global cache by using a JavaCompute node.

Monitoring and administration of the global cache or external grid

For more information, see Monitoring the global cache.