Do you want each consumer in a different thread?

They can share a thread pool. Really what I want is for each consumer to be able to process one message at a time, but N consumer to process N threads at once

When using Java I've used one channel per thread, I think I read it in the java api docs.

I saw that you could provide something like a threadfactory to langhor which might do something, but I wouldn't count on it handling concurrency (well) by itself

Apologies for a shameless plug - but it's coming from a good place 😉 My team's RabbitMQ client comes with multi-threading (and adjustable prefetch) support out of the box - and it's based on the Java client directly, rather than use Langhor (which we started with years ago). One caveat is that it has a hard-ish dependency on Component, but you can use it without it with relatively small effort: https://github.com/nomnom-insights/nomnom.bunnicula

Good on you for open-sourcing it! Looks good docs wise too. I'll give it a shot! 😃

My org quite recently moved towards using rabbitmq to "just do pub-sub" but it seems amqp + rabbit has quite a bit of complexity to handle, so having libraries with opinions is great.

Yeah, the amount of configuration options is quite overwhelming on the client and server side. We have basically set everything to be as safe as possible, while trading off throughput a bit (although we push 10s (or 100s now) of thousands of messages every hour and it's been fine. One thing to watch out for - there's v3 coming which will not be backwards compatible

Depends on use-case. If you’re expecting fast response to infrequent HTTP-requests then I’d probably pick CLJS. However I think the startup time is one of the smallest problems to solve when entering FaaS territory. 🙂

If you’re worried, you can write most of your code in cljc and easily swap between runtimes. 🙂

this new feature might change things a little https://aws.amazon.com/blogs/aws/new-provisioned-concurrency-for-lambda-functions/

@U6N4HSMFW could you elaborate on the other problems when using clojure with FaaS, I would be curious to know.

@U01HN2UCH9Q oh, I didn’t mean that Clojure would be a problem with FaaS. Actually I think the language itself is a great fit for FaaS. What I wanted to say is that in my experience people are too worried about startup penalty, which I perceive as a minor (technical) thing that can be worked around. I think there are more fundamental problems to be worried about, such as splitting the problem domain into distinct deployable artefacts and managing dependencies between them.

I don't think you are supposed to put anomalies inside an ex-info

You're supposed to return them instead. so you would not throw an anomaly, just return one

Do you return it? So, you don't use "let it crash"?

There is any good oss example of usage?

I make my functions return data->data. The caller still needs to check for success

Or let it crash if necessary

Or whatever policy you want

right. so caller may write it own msg to ex-info with a possibly generic error, and :cognitect.anomalies/message will came from "the cause"

What’s your goal?

ATM "just fun" https://gist.github.com/ericnormand/3a39e9093692b1ee3dbbb612d739e468#gistcomment-3575422

@U050ECB92 "The caller needs to check for success" sounds a lot like C return codes. I haven't really dealt with such an approach in Clojure. Does it not get overwhelming, to have to check the result in every single function that can get an "anomaly" from one of its callees?

result, _ := op();

Fwiw, datomic api uses anomalies and can be used for inspiration

I know, i catch some exceptions from there and I can dig into it. But as a non-oss, is harder to see

you can try the #cljfx channel. they're pretty helpful there.

Thx