Shindig can run in a very high volume environment -- the only thing you have to be careful about is how you implement your person/activity/appdata handlers. Sorting and filtering can be problematic, especially if your backend does not already do that for you. I have observed shindig servers pushing 600 req/sec on commodity hardware.
The built-in ehcache does quite well for smaller environments, a shared distributed cache like memcache would be recommended if you run a cluster. The gadget server can be separate from your container for the most part -- just make sure that it has low latency connectivity to your backend data. On Fri, Aug 7, 2009 at 12:10 PM, Priya Joseph <[email protected]>wrote: > > > Hi, > > I can't seem to locate any shindig scalability metrics. Can > you share? Can you share your lessons learnt scheme of things as well? > Isn't it amazing how we take battle-arrows-on-your-back for free lunch:) > > This > maybe a noob question - but do you recommend colocating the gadget > server where shindig is located?In the google gadget server > implementation, how are you colocated? And how do you split and amp > shindig caching with the usual portal caching layers? Looking for best > practice primarily, > > Thanks much, > Priya > > > > > > > > > >
