Product overview >
WebSphere eXtreme Scale can operate as an in-memory database processing space, which you can use to provide in-line caching for a database back-end or to serve as a side-cache. In-line caching uses eXtreme Scale as the primary means for interacting with the data. When eXtreme Scale is used as a side-cache, the back-end is used in conjunction with the data grid. This section describes various cache concepts and scenarios and discusses the available topologies for deploying a data grid.
- Cache architecture: Maps, containers, clients, and catalogs
With WebSphere eXtreme Scale, the architecture can use local in-memory data caching or distributed client-server data caching.
- Database integration: Write-behind, in-line, and side caching
WebSphere eXtreme Scale is used to front a traditional database and eliminate read activity that is normally pushed to the database. A coherent cache can be used with an application directly or indirectly using an object relational mapper. The coherent cache can then offload the database or backend from reads. In a slightly more complex scenario, such as transactional access to a data set where only some of the data requires traditional persistence guarantees, filtering can be used to offload even write transactions.
- Java object caching concepts
WebSphere eXtreme Scale is primarily used as a data grid and cache for Java objects. Use several APIs to interact with the eXtreme Scale grid to access and store these objects.
WebSphere eXtreme Scale overview
Cache integration overview
Transaction processing overview
REST data services overview
Tutorials, examples, and samples