Redvant: Difference between revisions
(→Précis) |
(→Précis) |
||
| Line 8: | Line 8: | ||
'''Redvant''' designates middle and front end software with red things and | '''Redvant''' designates middle and front end software with red things and | ||
[https://haskell-servant.readthedocs.io/en/stable/ <span style="color: pink;">servant</span>] | [https://haskell-servant.readthedocs.io/en/stable/ <span style="color: pink;">servant</span>] | ||
backend | middleware to access domain space backend services and a focus on incubation of the sameboat and tl:dr[AK] applications. | ||
<blockquote> | <blockquote> | ||
"red" could be | "red" could be | ||
Revision as of 22:50, 28 April 2019
Précis
Redvant designates middle and front end software with red things and servant middleware to access domain space backend services and a focus on incubation of the sameboat and tl:dr[AK] applications.
"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).
