Web Services Strategies
Beyond the technology, IT strategies for implementation of Web services by Doug Kaye.
|
Message Queuing--It's a Good Thing. Loosely coupled asynchronous web-services architectures based on message queuing not only offer improved reliability, they also allow you to handle high burst loads with less hardware and software. Here's an example of a web service that receives burst request loads of 150tps (when sampled each second) during the early-afternoon hours. But when front-ended with a messaging system (i.e., a huge buffer) the load can be handled by an application server and database that are only configured to process 50tps steady state. Even at the busiest time of day, this configuration never gets more than 30 seconds behind, which is well within the design criteria for the application. (Of course you could never do this with synchronous RPC-style web services.)
When averaged over 24 hours, the load for this web service is only 25tps (2.1 million transactions per day). If an 8-hour lag in message-queue processing were acceptable (as it is for some applications), a single 25tps application configuration could handle the whole thing.
Posted Monday, November 04, 2002 11:27:22 PM 
|
|
|
SIs Retool Web Services. The major systems integrators are organized by vertical practice units. Accenture, for example, has an insurance-industry practice among many others. This InfoWorld article finds that the SIs are, "converting years of best practices and intellectual property into prepackaged, tangible assets in an effort to make it easier for its network of integrators and consultants to deliver customized solutions."
Posted Monday, November 04, 2002 12:07:59 PM
|
|
|
|
|
|
