Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Skip to content
noob 0.1.2.dev232+g3ee3578 documentation
noob 0.1.2.dev232+g3ee3578 documentation

Contents:

  • Usage
    • Nodes
    • Tubes
    • Runners
    • Assets
    • Events
    • Config
    • ZMQ Runner
  • Examples
    • YAML Tube Config
  • API
    • asset
    • config
    • const
    • event
    • exceptions
    • input
    • introspection
    • logging
    • network
      • loop
      • message
    • node
      • base
      • gather
      • map
      • return
      • spec
      • tube
    • runner
      • base
      • sync
      • zmq
    • scheduler
    • state
    • store
    • testing
      • assets
      • nodes
    • tube
    • types
    • utils
    • yaml
  • Related Projects
  • Changelog
Back to top
View this page

Related Projects¶

Streaming processors¶

  • streamz

    • Nice examples of what pipeline systems need, even if it’s not exactly how we’d do them.

    • See, e.g. “zip” vs “combine_latest”

  • RxPY

  • Apache Kafka

    • good discussion of design, even if a very different application - massive scale, simple one-step processing replicated over many machines.

  • Apache Storm

  • streamparse

    • Toplogy DSL

Batch-based¶

  • Dagster

    • code locations interesting handling of multiple conflicting dep trees/environments in same pipeline: “just don’t specify the dependencies” (except in dagster+! where the cloud is the dependencies!) and specify the venv instead. each venv is independent and integrated over RPC

    • some analogies in division of labor: op -> node, graph -> tube, job -> tube + runner (not sure), i/o manager -> store…

  • luigi

  • dask.distributed

Next
Changelog
Previous
yaml
Copyright © 2025, raymond, jonny
Made with Sphinx and @pradyunsg's Furo
On this page
  • Related Projects
    • Streaming processors
    • Batch-based