The only reason I made a distinction is because we have been supporting an in-memory
backend in addition to Cassandra for a particular use case which is a developer working
with WildFly who wants to get up an running quickly. The biggest challenge I see with
right now with respect to domain mode or multi-node (i.e., multiple instances of
rhq-metrics service) deployments in general is coordination. We can implement a solution
that utilizes Cassandra in order to avoid additional external dependencies. Work on that
has not started but it is something I have been thinking about.
On Jan 9, 2015, at 10:44 AM, Heiko Braun
<ike.braun(a)googlemail.com> wrote:
when talking about wildfly, we need to consider both: standalone and domain.
this is a common mistake many contributors do and then they are surprised their potential
contribution is not accepted.
so for rhq-metrics, integrated into wildfly, it has to be all or nothing.
> On 09 Jan 2015, at 14:34, John Sanda <jsanda(a)redhat.com
<mailto:jsanda@redhat.com>> wrote:
>
> but let’s consider the single WildFly instance.
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel