Engula

Docs
Docs

Engula CodeProof

Engula CodeProof is a complete, Docker-runnable verification suite for validating the compatibility, client ecosystem, performance, stability, migration paths, platform matrix, and high-availability behavior of engula-server on a local machine or test environment.

It is not a single-purpose tool, but rather orchestrates the official Redis test suite, community client tests, benchmarking tools, and operations scenarios into a repeatable verification workflow. Each subitem generates its own report.html, making it easy for evaluators, delivery teams, and customers to review the results on site.

When to Use It

Scenario Recommendation
Quickly confirm Redis command compatibility for the first time Prefer Engula KernelCompat
Evaluate memory savings on real RDB data Prefer Engula ValueSight
Reproduce throughput, latency, or RDB save/load metrics Use Engula AutoBench or Engula RDBPerf
Run a PoC, version acceptance, or on-site customer reproduction Use Engula CodeProof

Coverage

CodeProof organizes verification items by suite:

  • compat: Compatibility for Redis 7.2 commands, protocol, Lua, transactions, Pub/Sub, Stream, persistence, ACL, CONFIG, modules, and more.
  • client: Compatibility for community client libraries such as Jedis, redis-py, go-redis, and node-redis.
  • perf: Throughput, latency, CPU, memory efficiency, RDB save/load, batch requests, and performance for non-string data types.
  • stability: Memory leak detection, long-run stability, crash recovery, BGSAVE stability, and more.
  • migration: RDB/AOF import, online migration, and migration result validation.
  • platform: Platform matrix covering Linux distributions, CPU architectures, containers, and more.
  • ha: Sentinel, Cluster, replication, reshard, hybrid deployment, and network partition recovery.

Recommended Path

  1. First read the Usage Guide to enter the TUI using the Docker image and run through a compat subitem.
  2. Then choose a suite based on your verification goal, for example running only compat, perf, or ha.
  3. Archive the generated report.html as acceptance evidence.
  4. For continuous regression, combine the open-source project documentation to integrate the command line, results database, or Web Dashboard.

Relationship to the Live Verification Dashboard

The website's Live Verification page displays the continuously running verification results from a public environment. The CodeProof documentation explains how to run the same kind of verification workflow in your own environment and generate auditable reports.

The public dashboard is ideal for quickly checking current results; local CodeProof is ideal for reproduction, parameter tuning, PoC, and delivery acceptance.

Getting Started

ON THIS PAGE