IBM Websphere eXtreme Scale is an in-memory data grid which was formally known as ObjectGrid. Caching requirements in Single threaded vs multi threaded applications, failure of singleton pattern and how data grids address the issue. Good start for novice folks. Once the basics are over, getting and deploying the WebSphere eXtreme Scale is as easy as dropping a jar file in the classpath. The examples start with the basic of how to an equivalent of ‘Hello World.
The example used is very lucid and easy to understand. The example covers how to create a grid and add and retrieve data. How does the data persistence work with Backup map and the different locking strategies available? The author has explained the locking and deadlocks very well. This topic is must read as these learning’s will be applicable when debugging and tuning the application data grid.
The Entity API allows the application developer to define the relationships so that ObjectGrid can understand the same. The author covers the Query API that provides an SQL-like view into an ObjectGrid The author demonstrates the usage of JPA API to showcase how the BackingMap is able to persist the data using the Loader. This chapter is a must read for all who want to introduce data grids in their existing applications.
The author details on the basic configuration required to start server instances, how to connect to a distributed object grid, managing the server/container load and tips on capacity planning. Must read for administrators, on how to tune data grids instances for effective performance and scalability.The chapters details on how to write agents that can send logic to the grid/shard.The patterns are generic and are applicable for any in memory data grid (IMDG) application.How the ObjectGrid instance are injected into spring and how to write interfaces using Spring managed declarative transactions.
No comments:
Post a Comment