We picked one that met our minimal requirements... our prototype was in Java however and that probably biased the choice a bit.
But for us it's an intermediate step. We need a more flexible solution. We will keep ActiveMQ in the picture to link different clusters (or an alternative) but for intra cluster processing we want something more in line with the contraints we need to meet especially regarding event serialization. We think that custom fit message serialization is not easily managed using a message bus generic layer. We need a more specific solution and some management hooks to deal with this in day to day operations. Luc On Tue, 2009-12-01 at 10:02 -0800, Daniel Werner wrote: > On Dec 1, 5:20 pm, Luc Préfontaine <lprefonta...@softaddicts.ca> > wrote: > > http://www.infoq.com/news/2009/01/clojure_production > > Slightly off-topic: > > What prompted you to choose ActiveMQ over other popular message bus > systems like RabbitMQ? Was it the ease of operability with Clojure/ > Java, or are there other strong factors? > -- 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
