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

BackingMap and Loader


The following problem does not exist in WebSphere eXtreme Scale version 7.0 and later. eXtreme Scale 7.0 solved the problem of writing data to a database out of order. The problem applies only to eXtreme Scale pre-7.0. The solution to this problem is left in as an example of using "soft references" to other objects and it remains a useful technique. We've seen that each BackingMap has its own instance of a Loader. Because each BackingMap uses the Loader to sync with the database according to its own conditions, we end up with different BackingMaps syncing at different times. Most of the time, we expect this to be a good thing. There are only four BackingMaps in our application that sync with the database (as seen below), but a larger application can have many more. Letting the BackingMaps sync on their own schedules reduces peak database load from an ObjectGrid instance.

Our PaymentProcessor application should be pretty fast again after enabling write-behind on the...