Proposed QIIME2 Roadmap

Thanks again.

This also seems like a good topic to discuss with an expert in HCI.

On (Sep-23-14|15:13), Evan Bolyen wrote:
> > +and duplication in defining multiple interfaces. Additionally it will allow
> > +remote execution over a network barrier (this would have been difficult to
> > +achieve with [pyqi](http://pyqi.readthedocs.org/en/latest/)).
> > +
> > +### Workers
> > +Once the _qiime-server_ has received a request via the protocol, it will launch
> > +a worker job to perform the computation. The _qiime-server_ will provide status
> > +updates to clients through the protocol. The worker job will record the results
> > +as an _artifact_ in a database.
> > +
> > +### Database
> > +**Note: This is not intended to be a substitute for the QIIME database
> > +project (QiiTA).** This is a discussion of how data will be organized and stored
> > +internally in QIIME2.
> > +
> > +The database represents a significant departure from the way QIIME currently
> 
> That is all true, but we do gain the ability of the interface to reason about composition if it has control of the artifacts in an abstract way. Perhaps a compromise is possible where a database simply logs the locations of files, but presently many of the files waste a lot of disk space by repeating what should be a relation to another table.
> 
> I think this is definitely something worth talking about over a call.
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/biocore/metoo/pull/4/files#r17943105