Hi Santosh, There's quite a bit of information on why these components have been chosen and where they are being used in the various OAE progress reports that have been produced [1, 2, 3, 4]. It might also be worth having a look at the slides [5] for the Bootcamp that was done at the Apereo Conference in San Diego.
More information can also be found on the Redis [6], RabbitMQ [7] and ElasticSearch [8] website, as we're basically using all of these components off the shelve and as they are intended to be used. [1] https://oae-community.sakaiproject.org/p/oQsfPoClaa/September%20Progress%20Report.pdf [2] https://oae-community.sakaiproject.org/p/oQsGlrMQaa/November%20Progress%20Report.pdf [3] https://oae-community.sakaiproject.org/p/oQUSwec4mg/Christmas%20Progress%20Report.pdf [4] https://oae-community.sakaiproject.org/p/pYK6vy0eie/April%20Progress%20Report.pdf [5] http://www.oaeproject.org/node/33 [6] http://redis.io [7] http://www.rabbitmq.com [8] http://www.elasticsearch.org Hope that helps, Nicolaas On 11 Aug 2013, at 17:58, Branden Visser wrote: > Hi Santosh, > > Redis is for caching, locking, broadcast messaging and activity aggregation. > > RabbitMQ is for task-based messaging, to distribute tasks like preview > processing, activity processing and search indexing to dedicated app > instances. > > Elastic search is, "you know, for search" ;) > > Hope that helps, > Branden > > Sent from my iPhone > > On 2013-08-11, at 9:12 AM, Santosh Kumar <[email protected]> wrote: > >> Hi >> I wanted to know when does Redis,rabbitmq,elstic search come in to >> picture in using Apereo oae . >> >> -- >> Regards >> ---- >> >> Santosh Kumar C S >> 8553631248 >> >>
_______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
