You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@usergrid.apache.org by "Jeffrey (JIRA)" <ji...@apache.org> on 2015/06/08 18:57:00 UTC

[jira] [Commented] (USERGRID-241) two-dot-o: Queue should not depend solely on AWS SQS

    [ https://issues.apache.org/jira/browse/USERGRID-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577468#comment-14577468 ] 

Jeffrey  commented on USERGRID-241:
-----------------------------------

Understood.  We have an in-memory queue option at this time and will pursue QPID in the future.

> two-dot-o: Queue should not depend solely on AWS SQS 
> -----------------------------------------------------
>
>                 Key: USERGRID-241
>                 URL: https://issues.apache.org/jira/browse/USERGRID-241
>             Project: Usergrid
>          Issue Type: Bug
>          Components: Stack
>            Reporter: David Johnson
>
> In the two-dot-o branch the faulty queue implementation has been replaced by a set of Queue interfaces and an AWS SQS implementation of those interfaces. 
> Usergrid should not depend on a commercial service and the Usergrid Launcher should be able to run standalone and without external services.
> So, what we need is a Queue implementation that we can embed in Usergrid for running JUnit tests that depend on the queue, for running the Usergrid Launcher and (ideally) one that can also be run remotely.
> Apache Qpid seems to be a good candidate for our default queue implementation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)