<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="">Oh, one more thing:<div class=""><br class=""><div><blockquote type="cite" class=""><div class=""><div class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div class=""><blockquote type="cite" class=""><div class="">On Feb 13, 2015, at 10:49 AM, Thomas Segismont <<a href="mailto:tsegismo@redhat.com" class="">tsegismo@redhat.com</a>> wrote:</div>...<br class="Apple-interchange-newline"><div class="">Hawkular metrics comes in two forms:</div></blockquote></div><div class=""><blockquote type="cite" class=""><div class="">* a Java library (metrics-core)<br class="">* a Java EE web application (built on top of the library)<br class=""><br class="">metrics-core can be embedded in any sort of JVM application but it<span class="Apple-converted-space"> </span><br class="">expects to find a Cassandra cluster somewhere.<br class=""></div></blockquote></div></div></div></blockquote></div><div class=""><br class=""></div>I understand that the collectors will be libraries; you’ll probably eventually want these in multiple languages. But it sure seems strange to have the Hawkular engine (for lack of a better term) be a library. Not only is that more complicated to set up, but if you design it to be embeddable then it will be harder to also make it scale.<div class=""><br class=""></div><div class="">It sure seems easier to focus on only installing Hawkular as a separate (potentially distributed) system that is set up and used. Sure, config it to point to the Cassandra cluster. But that can be easily wrapped up in a Docker image that people download and simply start, pointing via ENV variables to a Cassandra instance/cluster (perhaps also started from a Docker image). Better still is that these Docker images can be wrapped in a Kubernetes pod (that uses a Cassandra pod) and deployed on OpenShift. Now you have Hawkular as a service, but still easily installed on a customer’s network.</div><div class=""><div class=""><br class=""></div></div></div></body></html>