Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This is an excellent idea... but I'm a little put off by the reference implementation using DC/OS and Kafka... Its a little bit 'heavy' for a reference implementation, at least that's my personal preferences.

Id like to see a more 'low tech' version, or in the very least, a plan to transition from a 'heavy' reference implementation to a 'lighter' one once one became available since having a concise reference implementation makes porting and compatibility significantly easier.



Yes.

> To try it out yourself, you first need a to install a DC/OS cluster and then Apache Kafka...

When I see that, I know the cost of satisfying my curiosity is going to be a lot higher than I'm willing to pay right now.


Fair point, I suppose. Is https://dcos.io/docs/1.8/administration/installing/local/ an option?


Author here. Thanks for the feedback and I agree, a lighter ref impl would be ideal (it's just that I happen to use DC/OS on a daily basis so for me this was the most natural thing to do)

I'm all open for GitHub issues that capture this request and/or PR ;)


If you want simple named distributed pipes there is https://github.com/lukasmartinelli/pipecat . Which is basically cat over AMQP.


Agreed. I was expecting a low-fi example to point a dnpipe e.g.

$ mkdnpipe /tmp/a.fifo 192.168.1.10:123

With the target host running a dnpipe daemon.


Of course, one can already do that with socat, the multipurpose relay:

    socat PIPE:myfifo TCP-LISTEN:7766

    socat PIPE:myfifo2 TCP:192.0.2.1:7766


socat is great. You can also use OPENSSL-LISTEN and OPENSSL to replace TCP-LISTEN and TCP to get an encrypted SSL connection.


Interesting! Thanks for the tip


Agreed - personally would like to see either Arch, a BSD, or NixOS.


I'm put off by the domain name :p




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: