argoproj-labs/old-argo-dataflow

Maybe remove FIFO

alexec opened this issue · 3 comments

Rationale:

  • Not sure it will be used much
  • Does not support new lines in messages
  • Does not support meta-data
  • Does not vertically scale (unlike HTTP)

@alexec In case of pipeline with argo steps, does the FIFOs would make less performance impact? Having no additional http server for handling messages inside docker image used as steps could be a benefit on smaller platforms, I think.
btw. Do I understand correctly, that opening 'in' and 'out' FIFOs, satisfies container image contract in matter of readiness?

I don't expect FIFO will be faster, or slower. It just not as good as the other option.

Stale issue message