New and deprecated features in this release

WebSphere eXtreme Scale Product Overview > WebSphere eXtreme Scale overview

New and deprecated features in this release

WebSphere eXtreme Scale includes many new features in v7.0, including integration with the dynamic cache, byte array maps, and more.

What is new in WebSphere eXtreme Scale v7.0

Table 1. New features in WebSphere eXtreme Scale v7.0
Feature Description
Dynamic cache integration Dynamic cache: The dynamic cache provider allows applications that are using the WebSphere Application Server dynamic cache to leverage the advanced features and performance improvements of WebSphere eXtreme Scale. This feature results in a higher quality of service, linear scalability and high availability to bear on a broad variety of business applications with minimal invasive changes.
Byte array maps Byte array maps: With byte array maps, the application can store the value of a key-value pair in a byte array instead of object form, which reduces the memory footprint that a large graph of objects can consume.
WebSphere Real Time WebSphere Real Time: With support for WebSphere Real Time, the industry-leading real-time Java™ offering, WebSphere eXtreme Scale enables XTP applications to have more consistent and predictable response times.
Metric enablement Monitor with vendor tools: WebSphere eXtreme Scale includes implementations of metric access adapters to improve integration with IBM Tivoli Monitoring (ITM) and Hyperic HQ, enabling comprehensive insight into the operational behavior of business solutions. .
Dynamic maps Dynamic maps: Building multi-tenant applications has been greatly simplified. Map templates allow applications to create new maps on demand, avoiding the need to use application discriminators in the keys or creating extra maps that may never be used. .
Request timeout Request timeout WebSphere eXtreme Scale is enhanced to handle many of the common retry and exception logic tasks within the grid middleware. The request timeout for clients removes the burden from developers for boilerplate retry logic for most map interaction operations. Most retry-able conditions are now handled automatically, so you can focus on the business logic aspects of application development..
Composite index Composite index This feature can simplify index usage when querying multiple attributes and reduce the overhead of having multiple indexes defined. Query has also been optimized to take advantage of composite indexes. .

Deprecated features

Table 2. Deprecated features
Deprecation Recommended migration action
Partitioning facility (WPF): The partitioning facility is a set of programming APIs that allow Java EE applications to support asymmetric clustering. The capabilities of WPF can be alternatively realized in WebSphere eXtreme Scale.
StreamQuery: A continuous query over in-flight data stored in ObjectGrid maps. None
Static grid configuration: A static, cluster-based topology using the cluster deployment XML file. Replaced with the improved, dynamic deployment topology for managing large data grids.
Deprecated system properties: System properties to specify the server and client properties files are deprecated. You can still use these arguments, but change the system properties to the new values. See Properties file reference for more information.

Parent topic
WebSphere eXtreme Scale overview

+
Search Tips | Advanced Search

Feature	Description
Dynamic cache integration	Dynamic cache: The dynamic cache provider allows applications that are using the WebSphere Application Server dynamic cache to leverage the advanced features and performance improvements of WebSphere eXtreme Scale. This feature results in a higher quality of service, linear scalability and high availability to bear on a broad variety of business applications with minimal invasive changes.
Byte array maps	Byte array maps: With byte array maps, the application can store the value of a key-value pair in a byte array instead of object form, which reduces the memory footprint that a large graph of objects can consume.
WebSphere Real Time	WebSphere Real Time: With support for WebSphere Real Time, the industry-leading real-time Java™ offering, WebSphere eXtreme Scale enables XTP applications to have more consistent and predictable response times.
Metric enablement	Monitor with vendor tools: WebSphere eXtreme Scale includes implementations of metric access adapters to improve integration with IBM Tivoli Monitoring (ITM) and Hyperic HQ, enabling comprehensive insight into the operational behavior of business solutions. .
Dynamic maps	Dynamic maps: Building multi-tenant applications has been greatly simplified. Map templates allow applications to create new maps on demand, avoiding the need to use application discriminators in the keys or creating extra maps that may never be used. .
Request timeout	Request timeout WebSphere eXtreme Scale is enhanced to handle many of the common retry and exception logic tasks within the grid middleware. The request timeout for clients removes the burden from developers for boilerplate retry logic for most map interaction operations. Most retry-able conditions are now handled automatically, so you can focus on the business logic aspects of application development..
Composite index	Composite index This feature can simplify index usage when querying multiple attributes and reduce the overhead of having multiple indexes defined. Query has also been optimized to take advantage of composite indexes. .

Deprecation	Recommended migration action
Partitioning facility (WPF): The partitioning facility is a set of programming APIs that allow Java EE applications to support asymmetric clustering.	The capabilities of WPF can be alternatively realized in WebSphere eXtreme Scale.
StreamQuery: A continuous query over in-flight data stored in ObjectGrid maps.	None
Static grid configuration: A static, cluster-based topology using the cluster deployment XML file.	Replaced with the improved, dynamic deployment topology for managing large data grids.
Deprecated system properties: System properties to specify the server and client properties files are deprecated.	You can still use these arguments, but change the system properties to the new values. See Properties file reference for more information.