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