<div dir="ltr">Hi all<div><br></div><div>Firstly, apologies if this thread is intended for Redhat staff only.</div><div><br></div><div>My development background is primarily in .net - and so I am writing here to suggest using this instead - joking! chez.</div><div>But, while working with .net, microsoft release the Windows Communication Foundation framework - basically a framework for abstracting the different messaging systems - how messages are sent over the wire, or in proc - from the implementation. </div><div><br></div><div>For the past 5 years I have been almost exclusively working in Java and was delighted to see similar concepts in Jboss Switchyard and Apache Camel. In particular, Switchyard allows for a service to be exposed to the world via multiple bindings easily. Camel is also an excellent choice.</div><div><br></div><div>Personally I would love to see communication to Hawkular using Apache Kafka! Adding a kafak binding in either Switchyard or Camel is a breeze! </div><div><br></div><div>When it comes to choosing a messaging implementation, I have good success in choosing frameworks that focus on integration and abstracting the specific messaging type. In my company, when we have discussions of should we use rest or jms - we tend to say yes - the answer is in the question. We need a system that easily supports both, and more. </div><div><br></div><div>If this discussion arises now, it will surely arise again - therefore make the choice of easy integration. Abstract away how the message is sent to being simply a configuration. </div><div><br></div><div>Kind regards</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 10 November 2015 at 20:19, Lucas Ponce <span dir="ltr"><<a href="mailto:lponce@redhat.com" target="_blank">lponce@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> ><br>
> > So, communication via Java API should be feasible.<br>
><br>
> That is an option as long as it works in a distributed environment (think<br>
> containers and different JVMs; would Java API work there? and how?) and the<br>
> same interface that is currently exposed on the public REST API is<br>
> available.<br>
><br>
<br>
</span>I'm not thinking as a general option.<br>
<br>
But I have a wildfly server with metrics.war and alerts.war and mycomponent.war as client under same deployment, why I can't use Java API and I need to use REST between them ?<br>
<br>
EJB clients are also possible but this was not introduced before and I don't want to do it.<br>
<br>
But in the first scenario, looking for a user that wants to add its code colocated, the Java API should be the easy one.<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
_______________________________________________<br>
hawkular-dev mailing list<br>
<a href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">Anton Hughes<div><br></div></div></div></div></div>
</div>