Design Principles » History » Version 5
Tom Clegg, 04/02/2014 11:03 PM
| 1 | 2 | Tom Clegg | h1. Design Principles |
|---|---|---|---|
| 2 | 1 | Peter Amstutz | |
| 3 | (Work in progress) |
||
| 4 | |||
| 5 | 4 | Tom Clegg | * All Arvados core components are "free software":http://opensource.org/osd. |
| 6 | 5 | Tom Clegg | * Any application can run on Arvados, including non-free tools that are only available as binaries. Use wrapper scripts around vendor-provided source and binary distributions, rather than maintaining derivative works. |
| 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 | 5 | Tom Clegg | * Where possible, use established, widely understood components such as SSH, Git, Rails, and WebSockets rather than hand rolling custom components. |
| 10 | * Use Debian GNU/Linux as the primary supported deployment platform to ensure good performance, ease of development, and variety of deployment options. |
||
| 11 | 4 | Tom Clegg | * Use technologies such as virtualization and Linux containers to increase portability and flexibility of deployment. |