Proposed features

Notes on Proposed Features

NOTE This set of notes is drawn from various discussions (e.g. blogs, internal discussions) and represents a starting point for discussion, it is not intended to set anything in stone! We intend to assign owners to each feature, who will bring forward a much fuller proposal for consideration as time progresses.

NOTE There is a bias towards Infinispan here simply because this is the system with which the spec leads are most familiar! This does not mean an alternative product may not have a superior approach.

Async API (Future based)

See Infinispan's Async API

Distributed code execution

TODO

Map/Reduce

TOOD

Group API

See Infinispan's Group API.

CDI (Contexts and Dependency Injection) integration

See Infinispan's integration

Transactions (JTA) integration

TODO Determine what is already covered in JSR-107

• The ability to participate in transactions is necessary, both as an XA resource and as a simple cache to front a RDBMS, via JPA.
• Define behaviour at certain stages of a tx's lifecycle, particularly with regards to recovery
• Should play nice with JPA's second level cache SPI

Operation Mode

• Define and mandate REPLICATION and DISTRIBUTION, as well as SYNCHRONOUS and ASYNCHRONOUS versions of
  network communications
• Characteristics such as high availability, along with removal of single points of failure become increasingly important, since cloud infrastructure is inherently unreliable and can be re-provisioned with minimal notice; applications deployed on cloud need to be resilient to this.
• Further, one of the major benefits of cloud-style deployments is elasticity. The ability to scale out
  (and back in) quickly and easily.

Consistency Models

Configuration

• XML-based config file standardisation (including an XSD)
• Standardise programmatic config interfaces