Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

What’s new in 0.8

Engine 0.8.0 adds one attribute to the q: namespace, so a flow can choose the status and headers of a synchronous HTTP answer. The addition is backward compatible: a package written for 0.7 or 0.6 loads and runs unchanged. What changes on upgrade is listed in Upgrading to 0.8.0. 0.8.0 is also the first engine image since 0.6.25: 0.7.0 published no image, so everything in What’s new in 0.7 arrives with it.

FeatureWhat it gives youTry it
Outbound delivery no longer queues behind a slow destination (0.8.3)Each instance’s deliveries form their own ordered chain, under a global bound (sutra.outbox.workers, now 32) and a per-destination bound (sutra.outbox.destination-concurrency, 32). On a 3,500-row burst against a fast and a slow destination, the fast one’s p99 delivery lag went from 73.9 s to 166 ms. New metrics sutra.outbox.delivery.lag, sutra.outbox.in-flight, sutra.outbox.buffered.Watch outbound lag under a burst
AMQP 1.0 channels process deliveries concurrently (0.8.3)max-in-flight (default 16) intake calls per binding; a message is still accepted only after it is persisted, and 1 keeps the previous one-at-a-time behaviour. prefetch-count now sets the link credit.Channels
FEEL scopes without deep copies (0.8.3)Filters, quantifiers, for loops, context literals and function calls no longer copy the whole variable scope per item; results are identical.Rules
Status and headers on a synchronous answer<q:reply status="201"> (digits or FEEL) and the reply’s <q:header> children set the HTTP status and response headers, so a flow can answer like a REST API or an auth check.Answering with a status and headers
Broker outages as messagesWith sutra.engine.connectivity-events.channel set, each outage start and end the AMQP transport sees on a deployment’s channel reaches that deployment as a JSON message.Broker outages as messages
FEEL durations keep fractional secondsduration("PT0.001S") is one millisecond, not zero, through parsing, string(), arithmetic, comparison and .seconds.Durations with fractional seconds
No accepted message lost across a database restart (0.8.2)A data task that cannot reach its database (a restart breaks every pooled connection) now refuses the delivery for a retry (HTTP 503, broker redelivery, outbox backoff) instead of dead-lettering it, and a step that has run rides out a short outage before giving up, so it is recorded rather than run again. New code SUTRA.RUNTIME.DATASTORE.UNAVAILABLE.Data stores
The AMQP 1.0 sink keeps its connections (0.8.2)Up to 8 connections per broker (SUTRA_SINK_AMQP_MAX_CONNECTIONS), each with one session and a link per target, instead of a connection per message: on a durable queue 22.3 → 227 messages/s one at a time. Delivery guarantee unchanged.IBM MQ
The SQL audit sink writes in batches (0.8.1)With sutra.audit.sql on, the audit writer commits once per batch of up to 256 events instead of once per event, so on a durable PostgreSQL the journal keeps up with a busy engine (on a 50 orders/s relay workload it had been 85,770 rows, about five minutes, behind). Still best-effort and behind execution; nothing to configure.Audit sinks