AboutGetReadHelp

Operational characteristics

This page is part of a set of pages: "corepractice.org technical manual"
Turn the page:
Since the website is supporting only the Institute community not the wider user community, transactional loads may not be great. On the other hand, as we have no similar systems on which to model, we have no good indications either way. Another unknown factor that will influence growth of usage is how quickly regional chapters of IoCP will begin serving users directly with their own websites. Given that the Institute is a not-for-profit, we can expect some tolerance of performance issues, so long as they are not long-term.
Therefore it is proposed that hosting be purchased on a conservative performance basis, and upgraded or the provider changed only if necessitated by demand. An on-demand model would be useful.
On the other hand, integrity of the data is paramount. The website serves as the master repository of Core Practice.
Availability of the website is not critical: members will try again, and casual users can get content elsewhere.
Use of consumables is to be minimised: the system is expected to be essentially paperless, and products and services using paper or CDs are to be discouraged or avoided entirely.
This page is part of a set of pages: "corepractice.org technical manual"
Turn the page: