Interface Scheme
- All Known Subinterfaces:
CachingScheme,NamedTopicScheme,ObservableCachingScheme,ServiceScheme,TopicScheme<C,S>
- All Known Implementing Classes:
AbstractCachingScheme,AbstractCompositeScheme,AbstractJournalScheme,AbstractLocalCachingScheme,AbstractScheme,AbstractServiceScheme,BackingMapScheme,BaseGrpcCacheScheme,BaseGrpcScheme,CacheStoreScheme,CaffeineScheme,ClassScheme,ContinuousQueryCacheScheme,CustomScheme,DistributedScheme,DistributedScheme.BackupConfig,ExternalScheme,FlashJournalScheme,InvocationScheme,LocalScheme,NearScheme,OptimisticScheme,OverflowScheme,PagedExternalScheme,PagedTopicScheme,PagedTopicStorageScheme,ProxyScheme,RamJournalScheme,ReadWriteBackingMapScheme,RemoteCacheScheme,RemoteInvocationScheme,ReplicatedScheme,TransactionalScheme,ViewScheme,WrapperCachingScheme
public interface Scheme
A
Scheme defines the configuration information and necessary
builders for the construction of various well-known and identifiable
structures used by Coherence at runtime.
Coherence Schemes are best thought of as "templates" or "plans" that
are used for constructing runtime infrastructure. Common examples include:
services, caches, backing maps and cache stores.
Some Coherence Schemes, such as backing-map-schemes, are only used to
create maps, whereas as others, such as distributed-scheme are used to create
services, caches, and backing maps (as required by an inner scheme). In
addition, Coherence also provides Schemes that are unrelated to
caches and maps, such as invocation-scheme and cache-store scheme.
- Since:
- Coherence 12.1.2
- Author:
- pfm 2011.12.30