Clustered Caching with Tangosol Coherence II

Following on from yesterday:

  • Don’t use primitive types as keys. Create your own Opaque Immutable Type-Safe Key - don’t use Strings/Integers
  • Use the term Handle instead of key.
  • Locks are expensive as soon as your in a cluster - lock/unlock/get/put etc all incur a certain number of network hops
  • EntryProcessor’s cut down network hops
  • EntryProcessor’s are synchronous. Remember to increment the number of thread in Coherence from a performance perspective.
  • Distributed Caching Lessons
  • Deploy all your code to all the node in the Coherence cluster. Coherence is not a container!
  • Modeling: Aggregation  and association work fine in Coherence

~ by mdavey on January 16, 2007.

One Response to “Clustered Caching with Tangosol Coherence II”

  1. I am curious on the “Strings/Integers” comment. Both String and Integer (or Long) can be good key types. (I am guessing that there are reasons for creating your own as well, but I was just curious what the reason was in this case.)

    Peace,

    Cameron Purdy
    Tangosol Coherence: The Java Data Grid

Leave a Reply