Actions
Design Principles » History » Revision 2
« Previous |
Revision 2/7
(diff)
| Next »
Tom Clegg, 02/24/2014 11:01 AM
Design Principles¶
(Work in progress)
- Use only free software.
- Using the best tool, programming language, or framework for each component is preferable to standardizing on a single platform for the sake of conformity.
- Prefer to integrate established, widely understood components such as ssh, git, and slurm instead of hand rolling our own solutions.
- Use web technologies to tie components together, so programs can access Arvados regardless of programming language or framework.
- In the Arvados platform itself, explicitly make use of Linux and Debian specific features to maximize performance and ease of development.
- For applications that will run on the Aravdos platform, have minimal requirements and be able to run almost anything with just a wrapper script.
Updated by Tom Clegg almost 11 years ago · 7 revisions