All Classes and Interfaces
Class
Description
Non-blocking strategy for loading values from a backing data source into an async read-through
cache.
Non-blocking wrapper around
LoomClient that submits each operation to a managed thread
pool and returns a CompletableFuture.Application-facing async read-through helper.
Strategy for loading a single value from a backing data source into a read-through cache.
Immutable configuration for a single
LoomClient instance.Encapsulates the username and credential payload (password or token bytes) used to authenticate
a client connection.
Configuration for
FailoverLoomClient, specifying the ordered list of cluster
configurations to try when a connection fails.Controls how the client behaves when it loses its connection to the cluster.
Determines which cluster members the client sends requests to.
Configuration for periodic upload of client-side statistics to the cluster.
Live counters for the client's connection pool.
Provider of
ClientCredentials for each authentication attempt.Context passed to a
CredentialsFactory when the client needs credentials for a specific
cluster member.Notification that a named distributed object was created or destroyed in the cluster.
Listener notified when distributed objects are created or destroyed in the cluster.
A client that can switch between multiple cluster configurations when the current cluster becomes
unavailable.
Describes a secondary index to be created on a distributed map.
The kind of secondary index maintained by the cluster for a distributed map.
Snapshot of the cluster membership delivered once to a newly registered
InitialMembershipListener before any incremental add/remove events are sent.Extension of
MembershipListener that also receives the full membership snapshot when
first registered, before any incremental change events arrive.Notification of a change in the client or cluster lifecycle.
Callback invoked whenever the client or cluster lifecycle state changes.
Represents a phase in the client or cluster connection lifecycle.
Client-side handle to a linearizable distributed
long counter in the cluster.Accumulates multiple data-structure operations and submits them to the cluster in a single
network round trip.
High-level entry point for LoomCache's distributed data structures.
Primary synchronous client for a LoomCache cluster.
Factory for linearizable CP (consistency primitive) handles backed by a connected
LoomClient.Read-only view of a map entry together with its metadata, returned by
LoomMap.getEntryView(K).Client-side handle for submitting tasks to a named distributed executor in the cluster.
Client-side handle to a distributed grow-only set (CRDT) in the cluster.
Client-side handle to a cluster-wide unique ID generator.
Client-side handle to a linearizable distributed lock in the cluster.
Client-side handle to a linearizable distributed semaphore in the cluster.
Client-side handle to a distributed ordered list stored in the cluster.
Client-side handle to a distributed last-write-wins register (CRDT) in the cluster.
Client-side handle to a distributed map stored in the cluster.
Client-side handle to a distributed multi-map stored in the cluster.
Client-side handle to a distributed observed-remove set (CRDT) in the cluster.
Client-side handle to a distributed positive-negative counter (CRDT) in the cluster.
A composable query predicate that compiles to a SQL
WHERE fragment for LoomCache's native SQL
engine.Client-side handle to a distributed priority queue stored in the cluster.
A native query against a LoomCache map: a
LoomPredicate (the WHERE) plus optional
ordering and a row limit.An ordering column: an attribute and a direction.
A continuous-query cache (CQC) that maintains a local materialized view of the cluster entries
matching a given predicate.
Declarative configuration for a
LoomQueryCache (continuous query cache): the
continuous-query-cache knobs that a migrating workload depends on.Client-side handle to a distributed FIFO queue stored in the cluster.
Client-side handle to a durable, ringbuffer-backed publish/subscribe topic in the cluster.
Client facade for a native AP
ReplicatedMap: an eventually-consistent, fast-local-read map for
reference data.Client-side handle to a distributed ringbuffer stored in the cluster.
Client-side handle to a distributed set stored in the cluster.
Result of a SQL query executed against the cluster.
Client-side handle to a best-effort publish/subscribe topic in the cluster.
Thrown when a
LoomTopic message listener throws during message delivery.Client-side transaction facade.
Notification that a cluster member joined or left.
Listener notified when cluster members join or leave.
A standalone, in-process near-cache with configurable eviction, TTL, max-idle tracking, and
periodic cleanup.
Eviction algorithm used by the client-side near-cache when its maximum size is reached.
Determines how the near-cache is updated when the client writes a value to the cluster.
Configuration for the near-cache preloader, which persists the set of cached keys to disk and
reloads them on the next client startup to warm the near-cache without waiting for organic
traffic.
Configuration for the near-cache anti-entropy reconciliation pass.
Thrown when a multi-shard
putAll operation succeeds on some shards but fails on others.Concurrency-limiter for async operations that bounds the number of in-flight
CompletableFutures.Application-facing near-cache helper.
Generic application retry helper.
Thrown when a ringbuffer read requests a sequence that has already been overwritten.
A
CredentialsFactory that returns the same pre-configured ClientCredentials for
every authentication request.Policy that controls what happens when a
LoomReliableTopic ringbuffer is full.Timing and retry configuration for the background poll loop used by
LoomTopic
subscribers.Thrown when a topic consumer's sequence falls behind the ringbuffer head, meaning messages were
lost because the consumer could not keep up.
Application-facing write-behind utility.