# We put a Redis server inside our runtime

DevFeed: [We put a Redis server inside our runtime](<https://devfeed.tech/articles/we-put-a-redis-server-inside-our-runtime-17834.md>)

Original publisher: [Read original article](<https://encore.dev/blog/redis-runtime>)

Author: Ivan Cernja

Published: 2026-06-25T00:00:00Z

Content type: article

Language: en

Sources: [Encore Updates](<https://devfeed.tech/sources/encore-updates.md>)

Topics: [Redis](<https://devfeed.tech/topics/redis.md>), [Rust](<https://devfeed.tech/topics/rust.md>), [Development](<https://devfeed.tech/topics/development.md>), [Cache](<https://devfeed.tech/topics/cache.md>)

Tags: [cache](<https://devfeed.tech/tags/cache.md>), [development](<https://devfeed.tech/tags/development.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [redis](<https://devfeed.tech/tags/redis.md>), [rust](<https://devfeed.tech/tags/rust.md>), [scripting](<https://devfeed.tech/tags/scripting.md>), [streams](<https://devfeed.tech/tags/streams.md>), [transactions](<https://devfeed.tech/tags/transactions.md>)

## AI overview

Encore describes how its runtime provides an in-memory Redis server for local development and tests, aiming to keep behavior consistent with Redis in production. The Rust runtime embeds a port of miniredis as a library that supports commonly used Redis data types, streams, pub/sub, transactions, Lua scripting, TCP, and the Redis wire protocol.

## Source excerpt

How we run an in-memory Redis inside the runtime for local development and tests, and how we keep it behaving the same as the Redis you run in production.