Cameleering · projects

Projects: what is measured, and what is not yet

Each project rebuilds widely used software to carry the same load on less. A project shows numbers only once it has been measured against a named baseline on the same hardware; until then it shows its status and nothing else.

Cameleer Cameleered

An integration engine in the style of Apache Camel: Camel's routes, Enterprise Integration Patterns and YAML DSL as one std-only native binary with about 230 components, plus MCP tools for AI agents. Version 0.6.0. The first Cameleering project, and the one the practice is named after.

Measured on 2026-11-06 (version 0.4.0) against Apache Camel 4.23.0 on Java 21 and Apache Camel 4.22.1 on Quarkus native, same DigitalOcean c-4 machines: start-up 3 ms against 1.1 s on the JVM and 30 ms native; peak memory 4.8–54x less; throughput 1.7–8.7x. One loss: p99 for HTTP into Kafka, 8.6 ms against 7.8 ms.

Cameleer Ledger row Source

simoom Cameleered

An embeddable HTTP/1.1, HTTP/2 and HTTP/3 server engine in std-only Rust, with its own TLS 1.3 and no async runtime. Version 0.1.0 on crates.io (cargo add simoom). It replaces Cameleer's thread-per-connection HTTP server.

Measured from 2026-11-09 to 2026-11-12, first against cameleer-http, the server it replaces (CPU per request about 13 µs against about 23 µs, 43% less), then against 20 other HTTP servers on the same DigitalOcean c-4 droplets: first of 21 on start-up and first of 19 on CPU per request. Losses: plain HTTP 6% behind may-minihttp, TLS handshakes behind axum with rustls, HTTP/3 behind H2O.

simoom Ledger rows Source

karez Cameleering

Database connectivity shaped like JDBC, ODBC and ADBC, with Arrow results, in std-only Rust. A karez is an underground water channel. It is at the design stage: it has targets, and targets are not results, so it has no numbers here.

ksar planned

Cryptographic primitives and PKI in std-only Rust. A ksar is a fortified granary that keeps stores safe. It is planned and not started.

How a project gets here

It rebuilds software that many people run, keeping the names and behaviour they rely on.
It is measured against that software's current version on the same hardware, with a script anyone can rerun, and the losses are published with the wins (the method).
Numbers belong to the project that measured them: Cameleer's results say nothing about simoom, and the other way round.
A project carries the line "A Cameleering project" once its repository is public and it has a row in the ledger.

Common questions

Which projects are part of Cameleering?

Cameleer (integration engine, measured), simoom (HTTP server engine, measured), karez (database connectivity, design stage, targets only) and ksar (cryptographic primitives and PKI, planned).

Why do karez and ksar have no numbers?

Because they have not been measured. Cameleering's rule is no claim without a number: a target is labelled as a target and never shown as a result.