Fork me on GitHub

I need a rubber duck

🦆 8

what is the standard way of running a tcp server? java? aleph? is there something else?


Custom protocol or something standard?


custom protocol


My limited understanding is that everything uses a flavor of Java IO or NIO in the end, so that’s the lowest level you can get. For something more production ready, I’d look at aleph which wraps Netty.

👍 4

Are you looking for massive scale or just a proof of concept? Async IO is hard to work with, so I’d go first with a blocking flavor.


currently I am building a toy network to experiment with


distributed ledger stuff


In that case I’d go with blocking: is a simple wrapper.


It’s only 80 lines of code so you can easily just copy and modify as you see fit :)

❤️ 4

There doesn’t seem to be much activity there, googling for clojure tcp or clojure socket gives out a few results, which should be enough to get you started, but he focus I guess has shifted to async IO, which scales better but also can be a bitch to reason about some times. Perhaps though aleph provides a good way to deal with that.


the simple script will do for the time being, i'll have to grok the aleph abstractions further down the road then


aleph looks pretty good


blocking io is "easier" but it's a freaking pain to manage

👍 4

I am setting up a monorepo using deps + cli tool. I have used lein-monolith in a real-world project and comparing it to deps + cli I am not sure that lein monolith is offering much given the added complexity it introduces. Does anyone know if there is something lein-monolith can do that deps + cli cannot? I want to make sure I am not missing something