...
This anlaysis assumes the rational for co-location would be due to space limitations for additional servers here at the UC Davis campus. This does not address the issue of disaster recovery/high availability because that requires more architectural changes than simply running servers remotely.
Executive Summary
The current Kuali Rice architecture requires that Rice applications make direct database connections to the central Rice database for performance and transactional integrity of workflow documents. If client Rice applications are physically located a large distance from the Kuali Rice database there would be performance degregation for KEW transactions.
It is the technical workgroup's recommendation to keep all systems that are dependent on Rice located in the same physical location. As the Kuali Rice framework matures the database depenedey is expected to become less of a critical issue and then distributing the appliactions and RIce infrastructure may be technically fesable.
Kuali Application Issues to consider
Application Dependencies
Kuali Rice applications have three main depencenies on central infrastructure:
- Central Authentication
- Kuali Service Bus
- Kuali Rice database connection
Kuali KEW Architecture
Physical Data Center Issues to consider
Cost
The UC Davis San Diego Supercomputer Center (SDSC) Colocation Feasibility Study Report found that when amortized over 15 years the cost of co-locating at San Diego vs. building additional space on campus were nearly identical.
...