Difference between revisions of "TaskFlow/Architectures"
(→Architectures) |
(→Pumphouse) |
||
| Line 34: | Line 34: | ||
'''Why:''' | '''Why:''' | ||
| − | ''' | + | '''Links''' |
* https://www.mirantis.com/blog/pumphouse-deep-dive-part-1-2/ | * https://www.mirantis.com/blog/pumphouse-deep-dive-part-1-2/ | ||
Revision as of 07:36, 6 December 2014
Revised on: 12/6/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
What: http://wiki.openstack.org/wiki/Cue
Why:
Comments:
Cloud Big Data
What: http://www.rackspace.com/cloud/big-data/
Why:
Comments:
Pumphouse
What: https://github.com/MirantisLabs/pumphouse#pumphouse
Why:
Links
