Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Rust Implementation of Apache Burr

Abierto
  • ¿Algo no está bien?
#653 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
python, rust, wasm
Área
api, backend, observability

Línea de trabajo

Comienza revisando la implementación existente en Python y definiendo las golden/characterization tests propuestas en torno a ejecuciones registradas y salidas normalizadas. Construye el esqueleto del proyecto Rust mencionado y luego evalúa cada subsistema—runtime, persistence, telemetry, server/UI API y CLI—frente al objetivo de paridad establecido; terminado significa que los goldens acordados pasan y que se han decidido el alcance del proyecto y su ubicación en el repositorio.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area/core kind/feature priority/low

Is your feature request related to a problem? Please describe.

I’d like to use Burr’s state-machine / action-graph approach in environments where Rust is the primary deployment/runtime (e.g., Rust microservices, single-binary distribution, memory-safety requirements, low-latency workloads, WASM targets, etc.).

Currently this means either running Burr as a separate Python service, embedding Python, or re-implementing similar functionality ad-hoc, each of which adds operational complexity and makes it harder to standardize on Burr as a core orchestration primitive across a Rust-heavy stack.

Describe the solution you'd like

I’d like to propose (and happily help implement) an officially supported or officially endorsed Rust implementation of Burr with the goal of full functional parity with the existing Python implementation, including:

  • Core runtime parity: actions, transitions, state semantics, sync/async execution, parallelism features, hooks, typing system behavior, etc.
  • Persistence & tracking parity: same data model and on-disk formats where applicable, so recorded runs are comparable/portable.
  • Telemetry/observability parity: compatible tracing/metrics behavior (and the same conceptual execution events).
  • Tracking server + UI parity: ideally, the existing UI can be used unchanged by matching the server API contract.
  • CLI parity: equivalent commands/subcommands and behavior, or a clearly documented mapping.

Proposed Implementation approach:

  • Define the spec as golden/characterization tests derived from the reference implementation (recorded runs + normalized outputs).
  • Develop the test suite with a complete Rust project skeleton first.
  • Develop subsystem-by-subsystem until all goldens pass and expanding coverage until parity is reached.

Questions for maintainers:

  • Would this be welcome as an official multi-language implementation or preferred as a community project first?
  • If official, should it live in this repo (subdir/workspace) or in a separate repo?

Describe alternatives you've considered

  • Rust wrapper around Python Burr (PyO3 / embedding Python) to reuse existing behavior but with Rust entry-points.
  • Running Burr as a separate Python service and integrating over HTTP/IPC from Rust (keeps Burr unchanged, but adds runtime/ops overhead).
  • Partial Rust port (core runtime only) while keeping the existing tracking server/UI and/or persistence layer in Python.
  • Implementing only server/API compatibility in Rust while leaving runtime execution to Python (or vice versa).
  • Using other Rust state-machine/workflow crates instead of Burr (but that forfeits Burr’s model, tooling, and existing ecosystem).
Lenguaje dominante
Python
Estrellas
2.6k
Forks
203
Merge medio
3 d 10 h
PR fusionados (30 d)
6

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/burr

Todos los issues de apache/burr

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.