VMware GemFire

Cachegemfire

In-memory data grid of cache servers coordinated by locators.

Provider
default
Kind
Cache
Category
Data
Properties · 5 set by this component
propertytypevaluesrequiredkind defaultthis component
evictionPolicyenumlru | lfu | ttl | noneno—inherited
hashing · advancedenumnone | consistentnononeinherited
invalidationenumttl | event | nonenottlinherited
managedboolean—nofalse▸ false
materialised · advancedboolean—nofalseinherited
persistenceboolean—nofalse▸ false
readBarrier · advancedboolean—nofalseinherited
redundantCopies · component propertyinteger—no0inherited
regionType · component propertyenumpartition | replicate | localnopartitioninherited
replicationenumnone | single-az | multi-az | multi-regionnononeinherited
shardsinteger—no—inherited
structure · advancedenumkey-value | bloom-filter | hash-set | sorted-setnokey-value▸ key-value
tier · advancedenumcore | edgenocore▸ core
ttlJitter · advancedboolean—nofalseinherited
ttlSecondsinteger—no—inherited
usedAsPrimaryStore · advancedboolean—nofalse▸ false
Rules that apply · 3

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

cache-as-primary-store-without-persistence

This cache is the only copy of its data and has persistence turned off. A restart loses the data outright.

  • — all of these hold:
  • — the node's `usedAsPrimaryStore` is true
  • — the node's `persistence` is false
cache-missing-eviction-policy

A cache with no declared eviction policy inherits whatever the vendor chose, and most vendors default to evicting nothing. The cache fills up and then starts refusing writes.

  • — any of these hold:
  • — the node's `evictionPolicy` has no value
  • — the node's `evictionPolicy` is "none"
materialised-cache-without-rebuild-path

A cache holding materialised views has to be rebuildable from a durable store or a worker. With nothing feeding it, a cold cache is a permanent gap rather than a slow start.

  • — all of these hold:
  • — the node's `materialised` is true
  • — this does not hold:
  • — the node has at least one incoming edge from a sql-database, nosql-database, worker or stream
Use it in a design
nodes:
  - { id: "gemfire", component: "gemfire" }
Other Cache products · 36
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# VMware GemFire: in-memory data grid of cache servers coordinated by locators. Per the GemFire
# documentation region data is held in memory unless persistence is configured, and a partitioned
# region keeps no redundant copies unless `redundant-copies` is set.
schemaVersion: "1"
type: "component"
id: "gemfire"
kind: "cache"
provider: "default"
docs: "https://docs.vmware.com/en/VMware-GemFire/index.html"
defaults:
  managed: false
  persistence: false
  usedAsPrimaryStore: false
  structure: "key-value"
  tier: "core"
properties:
  regionType:
    type: "enum"
    values: ["partition", "replicate", "local"]
    default: "partition"
  redundantCopies:
    type: "integer"
    default: 0

The same page as markdown, for an agent: /catalogue/components/gemfire.md