Re: Hueniverse: Scaling a Microblogging Service - Part III49dba0a4cf15030cc61fbbc055bc4fb91Tue, 27 May 2008 15:43:25 +0800sharedcopy.comhttp://sharedcopy.com/images/logo-sharedcopy.png?V0SharedCopysupport@sharedcopy.comOnce the server is only serving data with limited scope, usually providing the messages of a single person with the optional perspective of the reader (to enforce access control), scaling becomes a much easier task as data can be segmented easier.http://www.hueniverse.com.sharedcopy.com/hueniverse/2008/04/49dba0a4cf15030cc61fbbc055bc4fb9.html#shcp1Tue, 27 May 2008 15:43:25 +0800Once the server is only serving data with limited scope, usually providing the messages of a single person with the optional perspective of the reader (to enforce access control), scaling becomes a much easier task as data can be segmented easier.choonkeat1trueif you only ask this once, the server side batch solution will be faster. But when the client starts asking this once a minute or more repeatedly, resources go to waste and scalability is more expensive.http://www.hueniverse.com.sharedcopy.com/hueniverse/2008/04/49dba0a4cf15030cc61fbbc055bc4fb9.html#shcp0Tue, 27 May 2008 15:43:25 +0800if you only ask this once, the server side batch solution will be faster. But when the client starts asking this once a minute or more repeatedly, resources go to waste and scalability is more expensive.choonkeat1true
Loading..