Tag
Engram is a Go binary backed by SQLite and FTS5 that gives coding agents persistent memory over MCP. It stores decisions and conventions between sessions, syncs through git and needs no Node, Python or Docker. Its search is lexical rather than semantic, and that shapes what you should save.
By default Docker limits neither the CPU nor the RAM of a container: a single one can exhaust the whole server. In Compose you bound them with deploy.resources.limits (cpus, memory) or the mem_limit and cpus shortcuts, and you control logs with the local driver, which rotates at 20 MB and 5 files by default.
Four and a half years after Rust officially entered Linux 6.1, with real Apple GPU and NVMe drivers in production and several public conflicts between maintainers, it is time for a sober technical balance. What works, what still costs, and where the next phase is heading.
Dragonfly is a Redis-protocol-compatible cache built on a multithreaded shared-nothing design with one thread per data shard, so an eight-core node uses all eight cores where Redis uses one. Its fork-free snapshot algorithm keeps latency flat while persisting. Ordinary clients work fine; modules like RedisSearch and RedisJSON are where compatibility frays.
Redis alone isn't a caching strategy, just an ingredient: picking the right pattern among cache-aside, read-through, write-through, and write-behind, sizing TTL to how fast data actually changes, invalidating explicitly for critical data, and mitigating thundering herd with jitter and locking are the decisions that actually matter in production.
