Design Principles » History » Version 3
Peter Amstutz, 02/24/2014 11:59 AM
| 1 | 2 | Tom Clegg | h1. Design Principles |
|---|---|---|---|
| 2 | 1 | Peter Amstutz | |
| 3 | (Work in progress) |
||
| 4 | |||
| 5 | 3 | Peter Amstutz | * All Arvados core components should be Free Software. |
| 6 | * Any application should be able to run on Arvados (possibly with a simple wrapper script) including non-free tools only available as binaries. |
||
| 7 | 1 | Peter Amstutz | * Use web technologies to tie components together, so programs can access Arvados regardless of programming language or framework. |
| 8 | 3 | Peter Amstutz | * Use the best tool, programming language, or framework for each component, instead of standardizing on a single platform for the sake of conformity. |
| 9 | * Prefer to integrate established, widely understood components such as ssh, git, and slurm instead of hand rolling our own solutions. |
||
| 10 | * Explicitly target Debian GNU/Linux as the deployment platform specific to maximize performance and ease of development. |
||
| 11 | * Use technologies such as virtual machines and Linux containers to enable portability for the software stack. |