Alginte 0.12.0 Beta
Released 2026-09-15.
Alginte is in beta (0.x): configuration keys, the topology export format, and APIs may change between releases; breaking changes are called out in release notes with migration guidance. 0.12.0 contains no breaking changes. Two deploy checks are stricter, listed under Behaviour changes below; both refuse topologies that failed at runtime before.
0.12.0 is the release for the JVM-native builder: run Alginte as a single JAR, write expressions from a reference that names what every field can see, call your own Java from them, and reset a stopped stream to any input position. Each item links to its documentation.
New
- The standalone JAR is downloadable: one file, the backend and the web UI, from the community repo's GitHub Releases with a SHA-256 beside it. Requires Java 25; the Docker image stays the recommended channel.
- The SpEL reference and cookbook: what every expression field can see, operator by operator; what each serde hands you for key and value; windowed keys; and eleven recipes with the record before and after, each one pinned by the fidelity corpus.
- Custom functions, the worked
example: a static Java method registered as a
#function, from the class to the container, with the four fail-fast messages explained. - Reset: move a stopped stream to an input position — earliest, latest, a timestamp or a per-partition offset — and start it, keeping its definition and its registration. The modal shows the server's plan before you confirm.
- The empty
observed table says what would fill it: the orphan internal topics the
cluster holds and the
DESCRIBEgrant on groups that would let Alginte name their applications.
Behaviour changes
- The editor's roots follow the runtime: an aggregate initializer has no record in scope and Map Values sees only the value. Both were accepted by the editor before and failed deployed; both are now rejected with a hint.
- A windowed key at a
sink is refused: after a window the key is Kafka's
Windowedobject, which no sink key serde can write. The canvas badges the sink while you draw and the deploy is refused, both naming the fix — a Select Key or a Map that unwraps it (validation as you build).
Fixes
- The tumbling-window example in the documentation sank its windowed key through a String serde and never produced a record; it now unwraps the key with a Select Key.
For operators
-
What one runtime token may push is bounded: pushes per second, snapshots and
events per push, and applications per token, each with a refusal that names
the limit. Four new
alginte.runtime.max-*properties on the configuration page; the defaults leave room for a thousand reporting instances on one token. - The JAR checks for updates the
way the image does, once a day at most, as an anonymous fetch of a small
manifest; set
alginte.update-check.urlto empty to switch it off.
Get it
docker pull alginte/alginte:latest Or the JAR (SHA-256), run with Java 25. Full install guide in the documentation — or try the playground: one command, no Kafka needed.