gasket-prometheus

Crates.iogasket-prometheus
lib.rsgasket-prometheus
version
sourcesrc
created_at2024-05-05 13:54:54.829675+00
updated_at2025-01-15 12:07:08.75362+00
descriptionPrometheus metric exporter for the Gasket framework
homepagehttps://github.com/construkts/gasket-rs
repositoryhttps://github.com/construkts/gasket-rs
max_upload_size
id1230232
Cargo.toml error:TOML parse error at line 18, column 1 | 18 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include`
size0
Santiago Carmuega (scarmuega)

documentation

https://docs.rs/gasket

README

Gasket

An opinionated Rust library for building application using data pipeline semantics. It uses a similar approach to the "Actor model", but fine-tuned for heavy, composable data processing.

Why

  • spliting data processing logic into small stages facilitates development (my own experience)
  • stages are easily composable
  • pipelines are a good abstraction for implementing observability
  • robust loops with error handling, backoff retries, etc are ubiquitous and hard to implement correctly
  • traditional async loops hide too much of the complexity, hard to optimice at scale

Goals

  • zero-cost abstraction (sort of)
  • staticly typed stages, dynamic composition of pipeline at runtime
  • developer has full-control over each work unit
  • robust work loop provided by the library
  • error handling out-of-the-box, with different policies (retry, exit, backoff)
  • fully observable out-of-the-box (metrics, traces)
  • multi-thread pipeline, async option inside stage
  • ergonomic pipeline setup
  • back-pressure out-of-the-box
  • hot swap of stages (add / remove)

Status

Current state of the lib is: "only I understand it". I'm experimenting with the api surface, so there are constant breaking changes happening frequently.

Commit count: 50

cargo fmt