Difference between revisions of "User:Zha Ewry/AWG: Desiderata for evaluating the proposed design"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
== This page captures some of the criteria I think would help evaluate proposed architecture designs == | == This page captures some of the criteria I think would help evaluate proposed architecture designs == | ||
'''This is a work in progress''' | |||
The page captures, in outline form some of the criteria we might use to evaluate choices in the architecture process. They are probably not earth shattering, but they should provide a nice starting point for discussion on how we make sure that what is being proposed is viable and well structured. | The page captures, in outline form some of the criteria we might use to evaluate choices in the architecture process. They are probably not earth shattering, but they should provide a nice starting point for discussion on how we make sure that what is being proposed is viable and well structured. | ||
| Line 17: | Line 19: | ||
Overall, all of these tests circle around making sure that we are keeping services, or small clusters of services as free from entanglement in other services as possible. | Overall, all of these tests circle around making sure that we are keeping services, or small clusters of services as free from entanglement in other services as possible. | ||
=== Packaging in different collections === | === Packaging in different collections === | ||
=== Plug and proxy models === | === Plug and proxy models === | ||
=== Securability of ineractions and components === | === Securability of ineractions and components === | ||
Revision as of 10:44, 18 September 2007
This page captures some of the criteria I think would help evaluate proposed architecture designs
This is a work in progress
The page captures, in outline form some of the criteria we might use to evaluate choices in the architecture process. They are probably not earth shattering, but they should provide a nice starting point for discussion on how we make sure that what is being proposed is viable and well structured.
Separation of concerns
This bucket includes looking at whether we have properly separated out the various parts of the system, and possibly, clustered them sensibly.
- Can we run a coherent system with as many services removed. In particular, can we pull services and only lose the functionality directly provided by the service.
- Can we run the service or cluster of services as a standalone service, without the rest of the system to support it.
- Can we plug replace the service with a different version of the service
- Can we run multiple copies of the service in the systemm
Overall, all of these tests circle around making sure that we are keeping services, or small clusters of services as free from entanglement in other services as possible.