Book Image

IBM WebSphere eXtreme Scale 6

By : Anthony Chaves
Book Image

IBM WebSphere eXtreme Scale 6

By: Anthony Chaves

Overview of this book

A data grid is a means of combining computing resources. Data grids provide a way to distribute object storage and add capacity on demand in the form of CPU, memory, and network resources from additional servers. All three resource types play an important role in how fast data can be processed, and how much data can be processed at once. WebSphere eXtreme Scale provides a solution to scalability issues through caching and grid technology. Working with a data grid requires new approaches to writing highly scalable software; this book covers both the practical eXtreme Scale libraries and design patterns that will help you build scalable software. Starting with a blank slate, this book assumes you don't have experience with IBM WebSphere eXtreme Scale. It is a tutorial-style guide detailing the installation of WebSphere eXtreme Scale right through to using the developer libraries. It covers installation and configuration, and discusses the reasons why a data grid is a viable middleware layer. It also covers many different ways of interacting with objects in eXtreme Scale. It will also show you how to use eXtreme Scale in new projects, and integrate it with relational databases and existing applications. This book covers the ObjectMap, Entity, and Query APIs for interacting with objects in the grid. It shows client/server configurations and interactions, as well as the powerful DataGrid API. DataGrid allows us to send code into the grid, which can be run where the data lives. Equally important are the design patterns that go alongside using a data grid. This book covers the major concepts you need to know that prevent your client application from becoming a performance bottleneck. By the end of the book, you'll be able to write software using the eXtreme Scale APIs, and take advantage of a linearly scalable middleware layer.
Table of Contents (15 chapters)
IBM WebSphere eXtreme Scale 6
Credits
About the Author
About the Reviewers
Preface

Optimistic collisions


A deadlock is a condition where two or more threads are waiting for a lock promotion on the same object due to the other threads holding a shared lock. Specifically, this happens when two threads hold an S lock on an object, and both threads then request an X lock to write changes to the object. The general case is that two threads attempt to simultaneously update a shared object resulting in lock contention because neither thread can obtain the higher-level lock it needs to write the changes.

The different locking strategies deal with this situation with some help from the developer. The optimistic locking strategy holds locks for very brief time periods. A lock is only held as long as it takes a thread to read or write an object. When thread 1 calls a get method for a payment with a key of 5000, the S lock is obtained for key 5000. After obtaining the lock, our payments BackingMap returns the object with that key and releases the S lock. This ensures that only objects...