GenStage defines the underlying message protocol, so in theory anybody could implement it and be compatible.
michalmuskala
CptnKirk
This defines a message protocol for interoperating with GenStage. It doesn’t provide a general stream processing API (with backpressure). That API shouldn’t require message passing.
So while this would help those wanting to communicate with GenStage only. A standard protocol would allow standard interop in both directions (Something ↔ GenStage ↔ SomethingElse).
1
CptnKirk
Also, GenStage itself is a useful user-level component abstraction, but Flows are likely where the interop would happen.
https://github.com/elixir-lang/flow
There is already interop within Flow to existing Elixir protocols like Enumerable. Now if Flow/GenStage were more protocol driven, it would be trivial to chain two completely separate projects together by integrating via the standard protocol.
Expose a function that turns a sink in one project into a standard publisher, then use this as a source in the next project. Each project has its own user-level component model and flow/graph abstraction but can integrate with any other project that implements the same underlying standard protocol. Just like many things are able to integrate via Collectable/Enumerable.
2