Analysis updated 2026-05-18
Replace hand-written glue code connecting Kafka or Pulsar to Delta Lake, Snowflake, or MongoDB.
Run ONNX machine learning models in-process on streaming records with an MLflow-managed registry.
Track which model version processed each record for regulated-industry audit requirements.
| intuitivedesigns/streamkernel-io | alexeygrigorev/codeforces-solutions-java | alexeygrigorev/rseq | |
|---|---|---|---|
| Stars | 1 | 1 | 1 |
| Language | Java | Java | Java |
| Last pushed | — | 2020-10-03 | 2016-11-25 |
| Maintenance | — | Dormant | Dormant |
| Setup difficulty | hard | easy | easy |
| Complexity | 4/5 | 1/5 | 2/5 |
| Audience | ops devops | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires Java 21 and typically Kafka or Pulsar plus a downstream storage system to be useful.
StreamKernel is a data pipeline runtime for the Java Virtual Machine (JVM) that handles moving and transforming data streams while enforcing policies and running AI models, all inside a single process. Instead of stitching together separate tools for policy checks, data transformations, AI inference, error routing, and delivery to multiple destinations, StreamKernel bundles those responsibilities into one configurable pipeline. The problem it solves: in most production data pipelines, teams end up writing "glue code" to connect message queues (like Kafka or Apache Pulsar) to storage destinations (like Delta Lake, Snowflake, or MongoDB), while also handling failed records, applying security policies, and tracking metrics. That glue is expensive to build and hard to audit. StreamKernel replaces it with a single process configured through a properties file, keeping source, policy, transformation, caching, inference, sink delivery, dead-letter queue routing, and metrics inside one runtime boundary. A notable feature is built-in AI enrichment: the pipeline can run machine learning models in-process using the ONNX format, integrated with the MLflow model registry. This allows a new model version to be promoted or rolled back without redeploying the pipeline, and each record can carry labels identifying which model version processed it, useful for regulated industries that require audit trails. The project is source-available: the core runtime is visible but private implementation details and model artifacts are withheld under a commercial license. It is written in Java and runs on Java 21. The full README is longer than what was provided.
A JVM data pipeline runtime that combines streaming, policy checks, and in-process AI model inference in a single configurable process.
Mainly Java. The stack also includes Java, ONNX, MLflow.
Source-available: the core runtime is visible, but some implementation details and model artifacts require a commercial license.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.