Case for Moodle
The LMS must be robust enough to serve the diverse needs of thousands of learners, administrators, content builders and instructors simultaneously.
Moodle and availability - [answer here]
The infrastructure should be able to expand or scale to meet future growth, both in terms of the volume of instruction and the size of the student body.
Moodle runs on a wide variety of webservers/database technologies. As with any installation of a server-based software system, it is crucial to refine carefully the choice of hardware, operating system, and database system, to ensure that the system can cope with a high throughput. The largest live Moodle installation at time of writing (Open Polytechnic of New Zeland) handles 45,000+ students and 6,500+ courses registered. There is a page about other large installations.
The consensus in the Moodle community seems to be that a Linux-based webserver running Apache, with PHP installed as well as a PHP accelerator, is commonly the best choice, and that the webserver and database server should sit on separate machines.
It should be possible to load-balance a Moodle installation, for example by using more than one webserver if necessary. The separate webservers should query the same database and refer to the same filestore area, but otherwise the separation of the application layers is complete enough to make this kind of clustering feasible. Similarly, the database could be a cluster of servers (e.g. a MySQL cluster).
All this implies that Moodle's architecture makes it easy to respond to future demand, by adapting the technologies upon which it runs. This should be possible even in a live setting, to improve the service without major disruption.
To support a host of automated and personalized services, such as self-paced and role-specific learning, the access, delivery and presentation of material must be easy-to-use and highly intuitive — like surfing on the Web or shopping on Amazon.com.
Moodle and usability - [answer here]
To support content from different sources and multiple vendors' hardware/software solutions, the LMS should exchange data using open industry standards for Web deployments (XML, SOAP or AQ).
Moodle and interoperability - [answer here]
The LMS infrastructure can reliably and effectively manage a large enterprise implementation running 24x7.
Moodle and stablility - [answer here]
As with any outward-facing collaborative solution, the LMS can selectively limit and control access to online content, resources and back-end functions, both internally and externally, for its diverse user community.
Moodle and security - [answer here]
- Building the case for Moodle Document forum discussion
- Why switch to Moodle when the university already supports BlackCT forum discussion