<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">This is interesting. I am not too familiar with ActiveMQ, and I just took a look at <a href="http://activemq.apache.org/masterslave.html" class="">http://activemq.apache.org/masterslave.html</a> that describes the master/slave configurations. To this point I have taken for granted that we have distributed messaging. But I have to ask, how are we planning on setting up/configuring distributed messaging?<div class=""><br class=""></div><div class="">Storm does require ZooKeeper and Spark has a cluster manager component which can be ZooKeeper.</div><div class=""><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On May 13, 2015, at 8:01 AM, Michael Burman <<a href="mailto:miburman@redhat.com" class="">miburman@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Hi,<br class=""><br class="">More like the bus is only a JMS topic with "distributed" not meaning probably what you hoped for. Since it's based on the ActiveMQ5 it's in HA configuration a single broker with master/slave (which with replicated LevelDB storage would then have ZooKeeper and everything else that's massively complex to manage). So nothing like the networks created by Hazelcast (eg. Vert.x underlying messaging infrastructure) / Storm / Spark / Cassandra / etc.<br class=""><br class="">These restrictions create their own headache when it comes to scaling in Kubernetes for example, but I don't think we need to solve this issue quite yet. Creating components without locking them to a JMS is the key forward however as that would allow changing the implementation if requirements dictate such in the future.<br class=""><br class=""> - Micke<br class=""><br class="">----- Original Message -----<br class="">From: "Juraci Paixão Kröhling" <<a href="mailto:jpkroehling@redhat.com" class="">jpkroehling@redhat.com</a>><br class="">To: <a href="mailto:hawkular-dev@lists.jboss.org" class="">hawkular-dev@lists.jboss.org</a><br class="">Sent: Wednesday, May 13, 2015 1:03:13 PM<br class="">Subject: Re: [Hawkular-dev] The components, glue and kettle<br class=""><br class="">-----BEGIN PGP SIGNED MESSAGE-----<br class="">Hash: SHA256<br class=""><br class="">On 05/13/2015 11:53 AM, Michael Burman wrote:<br class=""><blockquote type="cite" class="">I disagree with the fact where the actual bus-integration component<br class="">should reside. The components themselves should have the<br class="">capabilities of allowing another component to connect to their<br class="">internal "feeds" but the actual component -> bus connector should<br class="">be in the Kettle-repository. Why? The bus-connector is highly<br class="">dependent on the actual bus implementation. If we would change the<br class="">bus in any way in terms of implementation or API, it would require<br class="">changes to every Hawkular component (thus, they wouldn't be<br class="">decoupled by design) instead of only changing the implementation at<br class="">the bus-component.<br class=""></blockquote><br class="">I haven't worked with the bus yet, but isn't "the bus" just a synonym<br class="">for "a distributed JMS topic" ?<br class=""><br class="">- - Juca.<br class="">-----BEGIN PGP SIGNATURE-----<br class="">Version: GnuPG v2<br class=""><br class="">iQEcBAEBCAAGBQJVUyFhAAoJECKM1e+fkPrXKekH/2MFNSS+NYqP0v3uCNV3uY+J<br class="">/LYvrQptAXp/j0bUWkYR8rKPLedFTUiyZsZVW5DuwvwYEDMSDnlllaTKw2aQyawV<br class="">Z5xErHm4EYW+Q7cv5DO5ANZ3KZKufZhOlFxRYzG+zuZAoHNakWXgAhOqbW557l6R<br class="">AscC2EKGVmJQnFfjvw8aOaqc/Y2Bh/XuaMVfgGVeMXjpxSAzDP9iuxgfsXe4eEa/<br class="">gn0tSCVSPvWDfAKrEQOi5G35IKo0SuVVmM2rerww5CrPGXy2bLy25XC0RhXklhMW<br class="">f3D3ZbIk82Jl8QOOrJer3j2Py2t8s6nSTOPpyHf1+rI/qBICLPHMFvJ9ZgNpIlY=<br class="">=+U0e<br class="">-----END PGP SIGNATURE-----<br class="">_______________________________________________<br class="">hawkular-dev mailing list<br class=""><a href="mailto:hawkular-dev@lists.jboss.org" class="">hawkular-dev@lists.jboss.org</a><br class="">https://lists.jboss.org/mailman/listinfo/hawkular-dev<br class=""><br class="">_______________________________________________<br class="">hawkular-dev mailing list<br class="">hawkular-dev@lists.jboss.org<br class="">https://lists.jboss.org/mailman/listinfo/hawkular-dev<br class=""></div></blockquote></div><br class=""></div></div></body></html>