WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Global cache scenario: Caching static data

You can use a global cache to store static data. The use of a global cache facilitates horizontal scaling in situations where a cache is used to minimize network interactions to a back end system. With a global cache, you can increase the number of clients while maintaining a predictable response time for each client.

When WebSphere® Message Broker acts as a façade to a back-end database, it must provide short response times to the client, even though the back-end database has high latency.

Graphic showing the placement of the global cache in a multiple client scenario.

WebSphere Message Broker can provide short response times by caching results in memory (for example, ESQL shared variables).

Graphic showing the placement of the global cache in a multiple client scenario.

However, this configuration does not scale well horizontally. When the number of clients increases, the number of brokers and execution groups can be increased to accommodate the clients, but each broker has to maintain a separate in-memory cache.

Graphic showing the placement of the global cache in a multiple client scenario.

With a global cache, the number of clients can increase while a predictable response time is maintained for each client.

Graphic showing the placement of the global cache in a multiple client scenario.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:48:19


Concept topicConcept topic | Version 8.0.0.7 | bn23732_