Victor, So is the local state primarily for caching? On Wed, Jun 17, 2009 at 3:39 PM, Victor Kornov <[email protected]> wrote:
> And sync is just one side of scalability. Local state in case of > Velocity/memcache/rhino.dht just feats in nicely with messaging. > I'm sure you have read what Udi/Greg/Oren had to say on messaging cost and > ROI. If you know your system will gron in the number & complexity of the > features, it looks like one more pro for messaging. > > So, the biggest drawback is the tech risk of moving to highly different, > unknown system architecture. This requires un/re-learning assumptions and > approaches you take to building applications today. This coupled with not > having time is the showstopper for me as of now. > > On Thu, Jun 18, 2009 at 12:31 AM, Victor Kornov <[email protected]> wrote: > >> Anyway, problem with blocking RPC calls is your are hard capped on the >> amount of concurrent users. Caching does improve that. I really do not have >> numbers to tell what one can expect from this setup in "ideal" case. >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
