|
We have two major comments on overall architecture
|
|
Firstly it does not appear to include some commodity services such as collaboration, training, consultant interactions, (commodity) database, "personal web server"
|
Secondly it suggests a uniform architecture whereas we suggest designing for a hierarchical system supporting different protocols, performances and capabilities at each level or tier (terminology used later)
-
We suggest such a multi-tier architecture has significantly more flexibility and lower cost (in development and maintenance) as it enables commodity and HPCC systems to co-exist
-
We assume users want a mix of HPCC and commodity services which are often linked in a single session
|
