Documentation
¶
Overview ¶
Package main demonstrates why identifying the correct drum (constraint) matters in a pipeline. Three scenarios process the same work through parse → transform → store, where transform is 10× slower.
The demo tracks resource consumption over the pipeline's lifetime: total items in flight (aggregate WIP), estimated memory footprint, and per-stage queue depth.
Run:
go run ./examples/drum-demo/
Click to show internal directories.
Click to hide internal directories.