@Beta public interface CoordinationService extends PrimitiveService
This is a special type of PrimitiveService that differs semantically from StorageService in that
it supports cross-version backward/forward compatible storage. During upgrades, when nodes are running different
versions of the software, this service guarantees that cross-version compatibility will be maintained and provides
shared compatible primitives for coordinating across versions. Users must ensure that all objects stored in
primitives created via this service are stored using a serialization format that is backward/forward compatible,
e.g. using KryoNamespace.Builder.setCompatible(boolean).
atomicCounterBuilder, atomicCounterMapBuilder, atomicIdGeneratorBuilder, atomicValueBuilder, consistentMapBuilder, consistentMultimapBuilder, consistentTreeMapBuilder, documentTreeBuilder, eventuallyConsistentMapBuilder, getAsyncAtomicCounter, getAsyncAtomicIdGenerator, getAsyncSetMultimap, getAsyncTreeMap, getAtomicCounter, getAtomicIdGenerator, getDocumentTree, getTopic, getWorkQueue, leaderElectorBuilder, setBuilder, topicBuilder, transactionContextBuilder, workQueueBuilder