|
All content with label cluster+core-concept.
Related Labels:
failover
, write-through
, parallel-execution
, coherence-web
, continuous-query
, proxy
, production-environment
, availability
, c-w-archive
, service
, cache
, query
, faq-coherence-web
, session-cache-config
, mbeans
, replication
, local
, hardware
, versioned-backing-map
,
invocation-sevice
, re-entrant-calls
, data-access
, patterns
, manageability
, synchronous-events
, tcmp
, best-practices
, transaction
, cache-topolgies
, refresh-ahead
, session-management
, eis
, management
, cachestore
, serialization-cache
, query-based-execution
, scalability
, targeted-execution
, serviceability
, read-through
, death-detection
, invocation
, example
, multicast
, federation
, glossary
, write-behind
, overflow-map
, update-after-forums-move
, node-based-execution
, clients
, data
, singleton
, editions
, hashmap
, interleaving
, local-cache
, monitoring
, heap
, caching
, integration
, idempotency
, cache-topologies
, reliability
, listeners
, localcache
, serialization-map
, mutex
, failback
, sessions
, performance
, testing
, optimistic
, replicated
, topology
, agents
, http-session
, maplistener
, operating-system
, connection-pool
, mutext
, data-grid-wide-execution
, faq-code-examples
, security
, near-cache
, events
, servletcontext
, rtc
, backing-map
, fabric
, network
, aggregation
, httpsessioncontext
, architecture
, server
, partitioned
, faq-config
, member
, grid
, distributed
, synthetic-events
, local-storage
, read-write-caching
, load-balancing
more »
( - cluster
, - core-concept
)
Automatically manage dynamic cluster membership
(Coherence 3.4 User Guide)
Coherence manages cluster membership, automatically adding new servers to the cluster when they start up and automatically detecting their departure when they are shut down or fail. Applications have full access to this information, and can sign up to receive event notifications ...
|
Clustering
(Coherence 3.4 User Guide)
Coherence is built on a fully clustered architecture. Since "clustered" is an overused term in the industry, it is worth stating exactly what it means to say that Coherence is clustered. Coherence is based on a peertopeer clustering protocol, using a conference room model, in which servers ...
|
Cluster Services Overview
(Coherence 3.4 User Guide)
Coherence functionality is based on the concept of cluster services. Each cluster node can participate in (which implies both the ability to provide and to consume) any number of named services. These named services may already exist, which is to say that they may already ...
|
Cluster your objects and your data
(Coherence 3.4 User Guide)
Coherence is an essential ingredient for building reliable, highscale clustered applications. The term clustering refers to the use of more than one server to run an application, usually for reliability and scalability purposes. Coherence provides all of the necessary capabilities for applications ...
|
Coherence Caching Terminology
(Coherence 3.4 User Guide)
several terms which are used to describe the ability of multiple servers to work together to handle additional load or to survive the failure of a particular server. Basic terms Failover Failover refers to the ability of a server to assume the responsibilities of a failed server. For example, "When ...
|
|
|