Hi,

I agree it really depends what you're looking for. If you're especially 
looking for async performance then I think you can't go wrong with Pulsar 
<http://docs.paralleluniverse.co/pulsar/> which is a Clojure language 
integration module + a thin, idiomatic wrapper around Quasar 
<http://docs.paralleluniverse.co/quasar/> (which supports Java and Kotlin 
<https://kotlinlang.org/> for now, in future any JVM language). 
Quasar/Pulsar give you fibers 
<http://docs.paralleluniverse.co/pulsar/#fibers> (so no need for async APIs 
and related complications), Go-like channels 
<http://docs.paralleluniverse.co/pulsar/#channels>, Erlang-like actors 
<http://docs.paralleluniverse.co/pulsar/#pulsars-actor-system> and dataflow 
<http://docs.paralleluniverse.co/pulsar/#dataflow-reactive-programming>. 
You can also mix threads and fibers freely (there's an integration of 
java.util.concurrent 
<http://docs.paralleluniverse.co/quasar/javadoc/co/paralleluniverse/strands/concurrent/package-frame.html>
 
as well, should you be interested).

With Pulsar you can have automatic instrumentation 
<http://docs.paralleluniverse.co/pulsar/#automatic-instrumentation> and 
there are some useful Clojure/Pulsar-specific integrations in Comsat 
<http://docs.paralleluniverse.co/comsat/> already, like a jetty-fiber ring 
adapter <http://docs.paralleluniverse.co/comsat/#clojure-ring> and a fiber HTTP 
client based on httpkit 
<http://docs.paralleluniverse.co/comsat/#http-clients>. There's also a 
full-blown core.async <http://docs.paralleluniverse.co/pulsar/#coreasync> 
implentation based on fibers, so you don't need to use "go" block to have 
async-like performance.

vert.x <http://vertx.io/> itself now has an integration with Quasar called 
vertx-sync <http://vertx.io/docs/vertx-sync/java/> but for the moment is 
Java-only.

-- Fabio

On Sunday, January 3, 2016 at 9:59:39 PM UTC+2, adrians wrote:
>
>
> It used to be that Vert.x 2.x had integration for Clojure, but version 3.x 
> hasn't added it yet. Has anyone used this version through the Java API and 
> if so, how painful was it? Is Reactor <http://projectreactor.io/>any 
> better in that respect? What are people using when they want this kind of 
> back end?
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to