XC10: Show me the Cache (part 3)
MattO 2000005A7T Visits (1050)
The previous two articles described the WebSphere DataPower XC10 Appliance and how it can be used to offload cache from a JVM. I described two scenarios for the XC10. This article describes the final of the three scenarios. This scenario is different because the cache of the WebSphere DataPower XC10 appliance is more deeply integrated into the application layer.
In the final use case, the term "side cache" denotes that the cache is not directly in the path of requests to the database. The application is written to use the cache for retrieval of data. This scenario means that the XC10 is used for recently accessed data that can be served for an application from a data grid. This data grid provides cache storage, lookup, and retrieval. The cache data is indexed with name/value pairs and is stored in a standard ObjectMap.
The XC10 as side cace (For the DataPower 150)
This series of articles has described three scenarios for using the WebSphere DataPower XC10 appliance. In many situations the XC10 can be used without any changes required to the application code. In all of these scenarios, additional XC10 appliances can be added in a collective. This allows the cache capability to grow seamlessly. These scenarios show how a caching tier provides data much faster, reduces resources, and reduces the calls to the backend tier. The WebSphere DataPower XC10 appliance is a robust, drop in solution for a caching tier.
Growing the data grid
Bio and Contact Information
Matt Oberlin works for IBM in the WebSphere Education group. Matt enjoys providing complex technical information in a straightforward manner. You can find Matt at