[jira] [Resolved] (USERGRID-241) Index Queue should not depend solely on AWS SQS

["Michael Russo (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/USERGRID-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Russo resolved USERGRID-241.
------------------------------------
    Resolution: Fixed
      Assignee: Michael Russo

In-Memory queue is available and Usergrid is not dependent on AWS.  Other options will be available in the future for a Usergrid built distributed queue.

> Index 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
>            Assignee: Michael Russo
>            Priority: Minor
>
> 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)