...
- High Availability
Users of traditional web applications often have the expectation that service services will be available anytime. In order to provide this level of functionality, the underlying web services must be available 24 x 7. To that end, more work is required to understand what MIT web services need to be highly available, and how the services they rely on must be updated what updates they may require to meet this demand.
- Clarify Support
In order to provide a highly available service, the support procedure must be expanded to provide 24 x 7 response. In particular, an escalation path must be clearly defined in order to assure continues around the clock support.
- Data Latency
Any data latency issues due to source downtime or caching should be thoroughly documented. This will give developers a fuller understanding of the data they are using and allow them to create application applications that deal with known possibly data delays.
- Versioning
In order to provided a reliable and stable interface to developers, a versioning methodology should be agreed upon and utilized through throughout the project. Developers are encourage to learn from the versioning work currently be being done on other projects, include including Kuali Student and Kuali RICE. Also, IS&T must be ready commit to support supporting any released versions for the foreseeable future as applications tend to remain static one active for many years once deployed.
- Statistics and Reporting
The current method of gathering statistics should be reviewed and updated to allow for better and more robust reporting. This will allow for a better understanding of how current services are used and guide offer guidance were future development work may be needed.
- IS&T Standards
IS&T should develop a convention around web-services and development for IS&T services. Even with such a standard in place, services would still need to go through the TAP review process before going into production.
...