Jump to: navigation, search

Difference between revisions of "TaskFlow/Architectures"

(Architectures)
(Why)
Line 8: Line 8:
  
 
=== Architectures ===
 
=== Architectures ===
 +
 +
==== Cue ====
  
 
[[File:Cue-architecture.png|400px|thumb|left|Cue architecture]]
 
[[File:Cue-architecture.png|400px|thumb|left|Cue architecture]]
Line 13: Line 15:
  
 
'''What:''' http://wiki.openstack.org/wiki/Cue
 
'''What:''' http://wiki.openstack.org/wiki/Cue
 +
 +
'''Why:'''
 +
 +
'''Comments:'''
 +
 +
==== Big data ====
 +
 +
'''What:''' http://www.rackspace.com/cloud/big-data/
  
 
'''Why:'''  
 
'''Why:'''  
  
 
'''Comments:'''
 
'''Comments:'''

Revision as of 19:01, 3 December 2014

Revised on: 12/3/2014 by Harlowja

Why

Since taskflow creates a path toward stable, resumable, and trackable workflows it is helpful to have a small set of architectures (that have been implemented in real world scenarios) to help those implementing their own architectures. This allows users of taskflow to examine previously designed systems and to learn from the mistakes, choices, and reasons of those who have came before...

Note: this list will likely continue growing as new usages of taskflow emerge (and new features are introduced into taskflow), please feel free to add any of your own below.

Architectures

Cue

Cue architecture


What: http://wiki.openstack.org/wiki/Cue

Why:

Comments:

Big data

What: http://www.rackspace.com/cloud/big-data/

Why:

Comments: