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

Unsupported methods


You may have noticed that we are using the awkward convention of keeping track of the keys we use for payments in a BackingMap and using sequential integers as keys. We've use this convention up to now because the ObjectMap API does not include several methods implemented on java.util.Map. We can obtain a java.util.Map representation of an ObjectMap by calling the getJavaMap() method on an ObjectMap:

Map map = paymentsMap.getJavaMap();

This java.util.Map does not implement all of the methods specified by the java.util.Map interface. Most notably, this map does not have an implementation of the keySet(), entrySet(), or values() methods. In a typical Java application, a developer might get an entry set for a map and iterate over those entries with a for for each loop. The body of the loop would contain any business logic required of the objects in the map. This is a great approach for maps that fit in the main memory, but it does not scale to the size of maps that can be...