FalkorDB

Graph database backing Graphiti knowledge graph for the ORACLE Research Engine, providing entity-relationship storage.

Current State

FalkorDB deployed as oracle-falkordb container within the ORACLE Research Engine stack. Provides persistent graph storage for Graphiti MCP’s knowledge graph operations including nodes (entities), facts (relationships), and episodes (content snippets).

Key Learnings

  • oracle-research-engine-v1-deployed — ORACLE v1 deployment includes FalkorDB as graph store

  • traefik-multi-network-label-causes-504-on-recreate — oracle-graphiti-mcp was missing the traefik.docker.network label, causing intermittent 504s whenever FalkorDB recreate

  • floating-latest-docker-tags-resolve-differently-mid-upgrade — :latest Docker image tags are non-deterministic — they can resolve to different image digests between docker pull in

  • traefik-multi-network-504-missing-docker-network-label — When a container connects to multiple Docker networks, Traefik requires the explicit traefik.docker.network label to i

  • floating-latest-docker-tags-cause-silent-version-drift-mid-u — Docker Compose services using :latest tags can silently resolve to different image versions during an upgrade run if t

  • traefik-multi-network-label-missing-causes-504s — oracle-graphiti-mcp was missing the traefik.docker.network label, causing 504 gateway errors whenever FalkorDB recreat

  • dep-bound-images-graphiti-mirofish-hermes-not-optimizable — Large images for graphiti-mcp (5.65GB), mirofish (5.8GB), and oracle-hermes (4.72GB) are genuinely dep-bound: Neo4j+Falk

  • dep-bound-docker-image-bloat-not-worth-rebuilding — Large MCP server images (graphiti 5.65GB = Neo4j+FalkorDB+graphiti-core, mirofish 5.8GB = ML deps, oracle-hermes 4.72GB

  • dep-bound-image-bloat-not-worth-multi-stage-optimization — Some large Docker images (graphiti-mcp 5.65GB, mirofish 5.8GB, oracle-hermes 4.72GB) are dep-bound — docker history co

  • self-maintenance-discipline-at-every-layer-8-point-canonical — # Self-maintenance discipline at every layer — institutional pattern

Known Issues

(none)

Decisions

(none)

Relationships

Sources

  • Vault notes: 1 reference

Contradictions

(none)

graphiti | oracle | postgresql