coherence-pushreplication-pattern

The Push Replication Pattern Project Provides a mechanism to replicate cache entry events to other clusters and devices (including other clusters separated by WANs).

Overview

The Push Replication Pattern is a simple Cache Store (called a PublishingCacheStore) that leverages the Event Distribution Pattern to distribute and replay Cache Events in other clusters.

Revision History

Version 4.0.7 (changes since 4.0.6)

Version 4.0.7 resolves an issue where calling NamedCache.getAll(...) on a cache that is using Push Replication would throw an UnsupportedOperationExeception.

Version 4.0.6 (changes since 4.0.4)

Version 4.0.6 is a patch release to upgrade dependencies, those of which resolve both high-CPU and messages being left behind once acknowledged.

Version 4.0.5 was an internal unreleased version.

Version 4.0.4 (changes since 4.0.3)

Version 4.0.4 is predominantly a patch release to upgrade dependencies. However several other enhancements have been made.

Legend | = Fixed | = Breaking Change / Deprecation | = Improved | = New

• Upgraded to use latest Coherence Common and Coherence Event Distribution Pattern implementation.

• Added new functional tests for filtering transformers. Includes detailed example and configuration.

Version 4.0.3 (changes since 4.0.2)

Version 4.0.3 is predominantly a patch release to upgrade dependencies. However several other enhancements have been made.

Legend | = Fixed | = Breaking Change / Deprecation | = Improved | = New

• Upgraded to use latest Coherence Common and Coherence Event Distribution Pattern implementation.

• Added the "write-behind-delay" macro parameter to the distributed-scheme-with-publishing-cachestore scheme
  to allow parameterizing write-behind-delays. By default there is no delay as it's set to zero.

Care should be taken to avoid use of cache.remove when using write-behind-delay as it may cause publishing and out-of-order race-conditions.

• Resolves out-of-order publishing issue with the PublishingCacheStore when configured with write-behind.

• Resolves issue with PublishingCacheStore.storeAll method that treated updates as removes.

• Added new tests that utilize PublishingCacheStores using write-behind.

Version 4.0.2 (changes since 4.0.1)

Version 4.0.2 is predominantly a patch release to upgrade dependencies. However several other enhancements have been made.

Legend | = Fixed | = Breaking Change / Deprecation | = Improved | = New

• Upgraded to use latest Coherence Common and Coherence Event Distribution Pattern implementation.

• Improved functional tests for Event Transformers.

Version 4.0.1 (changes since 2.0.0)

Version 4.0.1 is predominantly a patch release to upgrade dependencies and support the up and coming Coherence release. Additionally however the following enhancements have been made.

Legend | = Fixed | = Breaking Change / Deprecation | = Improved | = New

• Re-introduced the coherence-pushreplicationpattern-cache-config.xml that was accidentally removed in the previous release.

• Enhanced the PublishingCacheStore implementation to adopt the underlying cache serializer for publishing events. This can significantly improve serialization performance, especially when using JMS-based infrastructure.

Version 4.0.0 (changes since 3.0.3)

This implementation of Push Replication is a radical departure from previous implementations. It now leverages the Event Distribution Pattern for all Event Distribution via Event Channels (previously known as Publishers).

The only class provided by this implementation is the PublishingCacheStore. All other implementation and configuration is made using the Event Distribution Pattern.

Further Documentation

• The Event Distribution Pattern
  The Event Distribution Pattern provides core infrastructure for Push Replication.