Yes - unless you specify using SNS/SQS it will use ‘LOCAL’ which is in-memory. Multi-DC or multi-region is an advanced use case, and I don’t think we have any documentation on how to actually deploy that, so the chances of people doing it are low.
That being said, we do need to document deployment topologies and considerations. Part of ongoing 2.x work will be to polish the docs and improve the startup experience for users/developers. -------------------------------------------------------------- Jeff West | Engineering | apigee <http://apigee.com/> | m: +1.214.450.9378 | twitter <https://twitter.com/jeffreyawest>@ <http://twitter.com/USERNAME>j <http://twitter.com/USERNAME>effreyawest @apigee <https://twitter.com/apigee> | Skype jeffrey.a.west > On Jan 15, 2016, at 3:41 PM, John D. Ament <[email protected]> wrote: > > Based on Dave's email, is it clear enough in the docs how to disable SQS > based distribution for those who do not deploy to AWS? Is off the default > option after building? > > On Fri, Jan 15, 2016 at 6:31 PM Dave <[email protected]> wrote: > >> On Fri, Jan 15, 2016 at 2:42 PM Michael Russo <[email protected]> >> wrote: >> >>> I just want to clarify the AWS dependency for queueing: >>> >>> Usergrid 2, at this time, depends on AWS for distributed queueing to >> allow >>> for complete, fault tolerant multi-region indexing with Elasticsearch. >>> There is an in-memory queueing service that works for single region >>> deployments. You can also technically deploy the Usergrid 2 application >>> itself in a multi-region fashion using the in-memory queuing for >> indexing. >>> This deployment would consist of having a single region Elasticsearch >>> cluster and each region's tomcat nodes pointing to the single ES cluster. >>> >> >> >> Awesome. I did not realize how well UG2 works without AWS SQS/SNS. >> >> Dave >>
