Concepts

How ematix-flow is put together. Why it exists, what's inside, and the mental model behind jobs, workflows, modes, and streaming.

Why ematix-flow

Eight lines on the back of the box — why ematix-flow exists.

Architecture

What's actually inside — Rust core, Arrow plane, Python surface.

Load modes

append, truncate, merge (scd1), scd2 — plus how merge keys are resolved and how watermarks work.

Streaming pipelines

Long-running consumers for Kafka / RabbitMQ / Pub/Sub / Kinesis with at-least-once delivery and DLQ support.

Delivery semantics & recovery

What ematix-flow guarantees under failure — crashes, restarts, rebalances, and slow or unavailable targets — and where the operator carries responsibility.