Service containers » History » Version 2
Peter Amstutz, 02/04/2025 08:09 PM
| 1 | 1 | Peter Amstutz | h1. Service containers |
|---|---|---|---|
| 2 | |||
| 3 | Concept: Containers launched via the Crunch infrastructure, but provide a network port that things can connect to. |
||
| 4 | |||
| 5 | 2 | Peter Amstutz | Arvados epic: https://dev.arvados.org/issues/17207 |
| 6 | |||
| 7 | 1 | Peter Amstutz | h2. Primary uses cases |
| 8 | |||
| 9 | 2 | Peter Amstutz | * Applications providing an API |
| 10 | ** a bunch of data needs to be loaded into RAM before it can be used, queried, or computed on |
||
| 11 | ** e.g. large language models, databases, function-as-a-service |
||
| 12 | 1 | Peter Amstutz | ** Makes sense when the time spent on any given query is much much smaller than the loading time |
| 13 | 2 | Peter Amstutz | |
| 14 | * User facing web applications |
||
| 15 | ** e.g. Integrative Genomics Viewer (IGV), Jupyter notebooks |
||
| 16 | ** Also includes web applications that interact with an API (first bullet) |
||
| 17 | |||
| 18 | h2. |