[Chapter-delegates] AMS - extremely slow and cumbersome - logs me out while waiting

[Paul Brooks]

On 15/04/2011 12:08 PM, Anne Lord wrote:
>
> As before, we will be consulting with the Chapter community and asking for
> volunteers to help specify requirements.  In fact a committee of volunteers was
> formed some time ago, but yes, we have not yet posted anything to the list as much
> work has been around the SAML/Shibboleth authentication piece.   For anyone with an
> interest in this subject and who has some time to help as part of the committee,
> please contact <chapter-support at isoc.org>.

A suggestion:

Requirement 1: Must provide acceptable responsiveness and performance across a 1000 ms
latency link.
Requirement 2: Development team must be required to create, develop and test  the
application from the end of a 1000ms latency link between them and the development server.

Explanation:
Several years past I was involved with development of a system that was required to be
accessed from around the globe. The developers created a classical triple-tier
database-driven java front-end and SQL back-end databases  that worked fine during
development and in HQ, courtesy of the dev team being located in a room next to the
server(s). Despite - or because of - following all the formal rules of scalable
architecture design, the application was so 'chatty' that it required several hundred
packet-round-trip-times to perform a transaction, and hence it was unusable outside
the continent on which the server(s) were located.

The above two requirements will ensure that particular fiasco isn't repeated here.

-- 
Paul Brooks
Internet Society of Australia
www.isoc-au.org.au