http://akfpartners.com/techblog/2009/05/12/scaling-availability-anti-patterns/ The Scalability Blog Tue, 10 Apr 2012 23:04:29 +0000 hourly 1 http://wordpress.org/?v=3.3.2 http://akfpartners.com/techblog/2009/05/12/scaling-availability-anti-patterns/#comment-131 Groovy On Grails Notes » Scalability Best Practices[转载] Mon, 24 Aug 2009 06:46:29 +0000 http://akfpartners.com/techblog/?p=245#comment-131 [...] - Use asynchronous communication when possible. Synchronous calls tie the availability of the two services together. If one has a failure or is slow the other one is [...] [...] – Use asynchronous communication when possible. Synchronous calls tie the availability of the two services together. If one has a failure or is slow the other one is [...]

]]> http://akfpartners.com/techblog/2009/05/12/scaling-availability-anti-patterns/#comment-130 构架设计的一些原则 « Cody Mon, 17 Aug 2009 07:32:11 +0000 http://akfpartners.com/techblog/?p=245#comment-130 [...] Asynchronous - Use asynchronous communication when possible. Synchronous calls tie the availability of the two services together. If one has a failure or is slow the other one is [...] [...] Asynchronous – Use asynchronous communication when possible. Synchronous calls tie the availability of the two services together. If one has a failure or is slow the other one is [...]

]]> http://akfpartners.com/techblog/2009/05/12/scaling-availability-anti-patterns/#comment-129 Scalability Best Practices | AKF Partners Blog Wed, 12 Aug 2009 01:51:37 +0000 http://akfpartners.com/techblog/?p=245#comment-129 [...] - Use asynchronous communication when possible. Synchronous calls tie the availability of the two services together. If one has a failure or is slow the other one is [...] [...] – Use asynchronous communication when possible. Synchronous calls tie the availability of the two services together. If one has a failure or is slow the other one is [...]

]]>