100 likes | 236 Vues
This document provides a detailed overview of the technical infrastructure that supports the web presence of Princeton University, highlighting its history, growth, and future aspirations. Starting from its inception in 1993 with limited resources, the infrastructure has evolved through various stages, including the introduction of user support and CGI services. It discusses server choices, project management strategies, and the ongoing challenges in maintaining and coordinating web resources. Future goals include developing an architected service that ensures reliability and adaptability in hosting.
E N D
Technical Infrastructure • History • www.Princeton.EDU running since 1993. • User website support announced 1994. • User CGI service added in 1997. • Organic, not architected. An Overview of the Princeton University Web
Technical Infrastructure • History (cont) • Today 42 Sites with www.???.Princeton.EDU An Overview of the Princeton University Web
Technical Infrastructure • Rationale for method • Initial platform choice based on support from Unix Systems. • Server choices based on server availability and ability to modify server for special uses • Growth by piecemeal addition and revolution • Look and feel buy-in An Overview of the Princeton University Web
Technical Infrastructure • Implementation • 1993 Two people less than 1 week • 2001 Many people many man months An Overview of the Princeton University Web
Technical Infrastructure • Resources • CIT • Departmental • Outside Services An Overview of the Princeton University Web
Technical Infrastructure • Project management • You stay out of my way and I’ll stay out of yours • Is there some way we can help you? An Overview of the Princeton University Web
Technical Infrastructure • Project maintenance • Its 10 pm, do you know what your data is? • How do I update without destroying access? An Overview of the Princeton University Web
Technical Infrastructure • Project success • No worse than many places • Success stymied by • Lack of coordination • Lack of standards • Lack of time An Overview of the Princeton University Web
Technical Infrastructure • Futures • Move to an architected service • Support true 24x7 where needed • Provide alternatives to machine upgrades to relieve performance problems • Provide ability to host anywhere transparently An Overview of the Princeton University Web
Technical Infrastructure • Futures (cont) • Continue to respond to outside world even when internal network down. An Overview of the Princeton University Web