iLabs' design separates online labs into three distinct modules connected by a Web service architecture.
- The Lab Server is operated by the lab's owner and deals with the actual operation of the lab hardware.
- The Lab Client runs on the end user's computer, and provides the interface to the operation of the lab.
- *The Service Broker*mediates exchanges between the Lab Client and the Lab Server and provides storage and administrative services that are generic and can be shared by multiple labs within a single university.
Based on the experiences of the different iLabs development teams The iLabs Project is developing a suite of software tools that makes it efficient to bring online and manage complex laboratory experiments. The iLabs Shared Architecture has the following design goals:
- Minimize development and management effort for users and providers of remote labs
- Provide a common set of services and development tools
- Scale to large numbers of users worldwide
- Allow multiple universities with diverse network infrastructures to share access
More information on MIT iLabs:
Motivation for iLabs
How to create your own iLabs
Administrators and Developers
Below is more information on iLabs' Architecture for Administrators and Developers:
- Administrators - How to set up and configure iLabs servers and brokers
- Developers - Developer information on programs and protocols used by iLabs