Hi all, a quick warning: this is very rough and early, and not yet ready for production use.<p>What we're aiming for is Unix-style composition. Because libswarm services communicate over unidirectional message streams (similarly to how goroutines communicate over channels [1]), they can be combined in a way similar to unix pipelines. This makes composition much easier, and is an elegant solution to the problem of hardcoded dependencies in service-oriented architectures (for service A to combine service B a C, it needs to know specifically B and C. Instead what you want the logic of A to be decoupled and re-usable with another component D, without changing it. That's what unix-style composition allows).<p>TLDR: libswarm allows network services to be composed like unix commands. But it's still very early!<p>[1] libswarm is built on a small library called libchan: <a href="https://github.com/docker/libchan" rel="nofollow">https://github.com/docker/libchan</a>