Skip to main content

Cache Service Guide

The Morio Cache Service (cache) provides data caching in Morio.

The cache is an in-memory data store, and is not persisted to disk. In other words, all cache data is ephemeral and will be lost when Morio restarts.

The cache service is a flanking service and optional. It will only be started when the tap service is configured in the Morio settings.

Cache service responsibilities​

The cache service was added to support the stream processing capabilities provided by the tap service.

It allows caching of recent data flowing through Morio, which in turn powers the Morio dashboarding features that are available through the UI service.

Access to the cache service​

The cache service is not exposed as an external service. In other words, Morio does not provide a Redis-like service that you can utilise for non-Morio use-cases, like our (persistent) KV store.

Instead, the cache service is available internally to the tap service. Externally, you can read cache keys through the API service, but writing to the cache is not supported outside the tap service.

Under the hood​

The cache service is powered by ValKey — the open source Redis fork.