Redvant: Difference between revisions
(→Story) |
No edit summary |
||
| Line 14: | Line 14: | ||
react, redux, redis, or just plain red, a simple name. | react, redux, redis, or just plain red, a simple name. | ||
</blockquote> | </blockquote> | ||
and "vant" is just from haskell-servant. | |||
</blockquote> | </blockquote> | ||
Stands for otherwise unnamed consumer product development flows in my public job shop outside of the DDD process. | |||
{{TOCright}} | {{TOCright}} | ||
| Line 22: | Line 23: | ||
= Story = | = Story = | ||
Redvant is a name for a | Redvant is a name for a dev workflow defined by an implementation path from front end thru DCMS middleware, to arbitrary domain space function, but particularly Apache ISIS based end consumer apps such as GT2 and TASKPM. | ||
Ideally, the layers of | Ideally, the layers of any mediating app between these endpoints would be developed from first DDD principles. Practically, besides the GT2 and TASKPM exemplars, just doing it and getting it done to a useable state is the good here. | ||
Practically, | |||
== Residue/Result == | == Residue/Result == | ||
Revision as of 02:15, 19 April 2019
Précis
Redvant is purescript-react, red FE with servant backend as a focus/incubator for DCMS and tl:dr[AK] apps.
"red" could be
react, redux, redis, or just plain red, a simple name.
and "vant" is just from haskell-servant.
Stands for otherwise unnamed consumer product development flows in my public job shop outside of the DDD process.
Story
Redvant is a name for a dev workflow defined by an implementation path from front end thru DCMS middleware, to arbitrary domain space function, but particularly Apache ISIS based end consumer apps such as GT2 and TASKPM.
Ideally, the layers of any mediating app between these endpoints would be developed from first DDD principles. Practically, besides the GT2 and TASKPM exemplars, just doing it and getting it done to a useable state is the good here.
Residue/Result
- ISIS Common DS platform builds for
GT2, TASKPM, and SB apps, forming DDD product line engineering flows
with standard timeline(s) (e.g.: biz case 64) as domain driven job streams in the
Public Job Shop (PJS).
