OCI Cache with Valkey

ociCacheoci-cache-valkey

Managed Valkey clusters with a private TLS-only endpoint, sharded or non-sharded.

Provider
oci
Kind
Cache
Category
Data
Properties · 3 set by this component
propertytypevaluesrequiredkind defaultthis component
clusterMode · component propertyenumnon-sharded | shardednonon-shardedinherited
engineVersion · component propertyenumvalkey-7-2 | valkey-8-1novalkey-8-1inherited
evictionPolicyenumlru | lfu | ttl | noneno—inherited
hashing · advancedenumnone | consistentnononeinherited
invalidationenumttl | event | nonenottlinherited
managedboolean—nofalse▸ true
materialised · advancedboolean—nofalseinherited
nodeCount · component propertyinteger—no—inherited
persistenceboolean—nofalse▸ false
privateEndpointOnly · component propertyboolean—notrueinherited
readBarrier · advancedboolean—nofalseinherited
replicationenumnone | single-az | multi-az | multi-regionnononeinherited
shardsinteger—no—inherited
structure · advancedenumkey-value | bloom-filter | hash-set | sorted-setnokey-value▸ key-value
tier · advancedenumcore | edgenocoreinherited
tlsOnly · component propertyboolean—notrueinherited
ttlJitter · advancedboolean—nofalseinherited
ttlSecondsinteger—no—inherited
usedAsPrimaryStore · advancedboolean—nofalseinherited
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: "cache-valkey", component: "oci-cache-valkey" }
Other Cache products · 36
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# OCI Cache with Valkey: the same managed cache service running the open source Valkey engine.
# "About OCI Cache" lists Valkey 8.1 (the recommended version) and Valkey 7.2, and states a non-sharded
# cluster carries one primary and up to four replicas while a sharded cluster has three or more shards.
# TLS-only connections over a private endpoint apply to Valkey clusters as they do to Redis ones.
schemaVersion: "1"
type: "component"
id: "oci-cache-valkey"
kind: "cache"
provider: "oci"
docs: "https://docs.oracle.com/en-us/iaas/Content/ocicache/overview.htm"
defaults:
  managed: true
  structure: "key-value"
  persistence: false
properties:
  engineVersion:
    type: "enum"
    values: ["valkey-7-2", "valkey-8-1"]
    default: "valkey-8-1"
  clusterMode:
    type: "enum"
    values: ["non-sharded", "sharded"]
    default: "non-sharded"
  nodeCount:
    type: "integer"
  tlsOnly:
    type: "boolean"
    default: true
  privateEndpointOnly:
    type: "boolean"
    default: true

The same page as markdown, for an agent: /catalogue/components/oci-cache-valkey.md