Design Principles » History » Revision 3
Revision 2 (Tom Clegg, 02/24/2014 11:01 AM) → Revision 3/7 (Peter Amstutz, 02/24/2014 11:59 AM)
h1. Design Principles (Work in progress) * All Arvados core components should be Free Software. * Any application should be able to run on Arvados (possibly with a simple wrapper script) including non-free tools Use only available as binaries. free software. * Use web technologies to tie components together, so programs can access Arvados regardless of programming language or framework. * Use Using the best tool, programming language, or framework for each component, instead of 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. * Explicitly target Debian GNU/Linux as Use web technologies to tie components together, so programs can access Arvados regardless of programming language or framework. * In the deployment Arvados platform itself, explicitly make use of Linux and Debian specific features to maximize performance and ease of development. * Use technologies such as virtual machines For applications that will run *on* the Aravdos platform, have minimal requirements and Linux containers be able to enable portability for the software stack. run almost anything with just a wrapper script.