There's an onyx-kafka plugin I believe, so you should be in luck!
On Fri, Jun 30, 2017 at 10:25 PM, Derek Troy-West
wrote:
> I still have Storm topologies in prod, but I'm investigating Kafka Streams
> and Onyx right now.
>
>
> On Saturday, July 1, 2017 at 9:38:08 AM
I still have Storm topologies in prod, but I'm investigating Kafka Streams
and Onyx right now.
On Saturday, July 1, 2017 at 9:38:08 AM UTC+10, Bobby Calderwood wrote:
>
> Onyx is super cool, has matured substantially, and has a great team behind
> it.
>
> I've also had success building with
Onyx is super cool, has matured substantially, and has a great team behind it.
I've also had success building with Kafka (and its ecosystem libraries Kafka
Connect and Kafka Streams) and Datomic.
Cheers,
Bobby
--
You received this message because you are subscribed to the Google
Groups
I'd have to know a little bit more about the specifics of your message
driven architecture to say for sure, but in general I'd still highly
recommend Onyx over Storm. In the last two years the Distributed Masonry
crew have done a TON of fabulous work with Onyx, including closing the
performance
This thread is a bit old, but it's seen two year awakenings before... and
still shows up high in google searches.
I wonder how you folks see it now. Onyx is a bit older by now, and not much
seems new out there. What would you choose for reliable and resilient
distributed computing with clojure,
http://docs.paralleluniverse.co/pulsar/ is out there. I can't say I've used
it in anger, but I did enjoy experimenting with it.
On Sun, Jul 19, 2015 at 11:24 AM Colin Yates colin.ya...@gmail.com wrote:
I don’t have anything to add at that scale, but I wanted to echo Stuart’s
comment about the
This is an old thread, but it showed up in my Google Groups so I figured I
would give an answer.
I have worked on fairly large (10-50 machines) distributed systems written
entirely in Clojure.
The language itself doesn't provide an explicit mechanism for communication
between machines, so you
Thanks Stuart for your answer, it is very helpfull. Would you choose
Clojure again ?
2015-07-19 17:13 GMT+02:00 Stuart Sierra the.stuart.sie...@gmail.com:
This is an old thread, but it showed up in my Google Groups so I figured I
would give an answer.
I have worked on fairly large (10-50
Absolutely would use again. But I'm biased towards Clojure already. :)
–S
On Sunday, July 19, 2015 09goral wrote:
Thanks Stuart for your answer, it is very helpfull. Would you choose
Clojure again ?
2015-07-19 17:13 GMT+02:00 Stuart Sierra:
This is an old thread, but it showed up in my
I don’t have anything to add at that scale, but I wanted to echo Stuart’s
comment about the serialisability of EDN. Moving EDN between the front and back
tiers on our app has cut down a bunch of boilerplate. That principle can scale
across machines as well.
On 19 Jul 2015, at 16:54, Stuart
I'll also add that if you're interested in the Storm model (distributed
stream processing), you may want to check out Onyx
(https://github.com/onyx-platform/onyx). It's newer, but I have a feeling
that moving forward we're going to see it take a dominant position as far
as that flavor of
David,
Have your opinion on Akka changed since 2013 now that you have seen its
progress ? I am very interested in your opinion.
Regards,
Mateusz
W dniu czwartek, 4 lipca 2013 11:39:46 UTC+2 użytkownik David Pollak
napisał:
Please keep in mind that Scala's Actor Model is a very thin piece
Hi
I'm surprised nobody mentioned storm yet. It's massively scalable real-time
computing, using clojure.
Le 3 juil. 2013 16:18, Softaddicts lprefonta...@softaddicts.ca a écrit :
clj-zookeeper + avout. We run our solution on clusters of small nodes, we
needed
a lightweight solution. We
Please keep in mind that Scala's Actor Model is a very thin piece of code
that is not inherently distributed.
There are a ton of issues in Scala related to crossing address spaces.
Scala is not nearly as biased to immutability as Clojure. Sure, there are
case classes, but case classes can easily
Not that I'd recommend using it in production, but I experimented with
distributed reference types on top of Redis some time ago:
https://github.com/lantiga/exoref
Several aspects are very rough e.g when the connection to Redis is lost or
when it comes to reusing a key.
Overall it's probably
I'd like to hear others opinions on this too. I don't believe Clojure has
anything built in at this point. My plan of action (not yet implemented) is
to use gearman(possibly java, but it seems that it is no longer updated)
and zeroconf for clusters (just for automatic master determination).
I
clj-zookeeper + avout. We run our solution on clusters of small nodes, we needed
a lightweight solution. We implemented cluster queues and use avout locking.
Our configuration is also stored in zookeeper as clojure expressions.
We isolated this in a coordinator module so nothing spills out in the
17 matches
Mail list logo