oodt-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From BW <b.du...@gmail.com>
Subject Re: Quality-Risk-Trade-off
Date Mon, 23 Jan 2012 15:28:34 GMT

> Quality: Usability : High Priority
> Architectural aspect supporting Usability:
> Components and the data flow related to servicing the user needs:
> Client/Server components wrapped in a web app that is deployed to a tomcat server
> where REST services are provided through an end point.
> Performance wise, the communications are synchronous where blocking on the user
> client side occurs until the thread of the service invocation completes.
> Associated Risk:
> Extremely large data transfers will force the user to wait until thread involved
> in servicing user completed resulting in user dissatisfaction and a decrease in performance.
> Approach Trade Off:
> Synchronous blocking communications are more manageable and are not as complex as
> asynchronous communications resulting an increase in maintainability and development

  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message