Redvant: Difference between revisions
(→Story) |
(→Précis) |
||
| Line 12: | Line 12: | ||
"red" could be | "red" could be | ||
<blockquote> | <blockquote> | ||
react, redux, redis, or just plain red, a simple name. | react, redux, redis, or just plain red, a simple name as in red5 or the parfume. | ||
</blockquote> | </blockquote> | ||
and "vant" is just from haskell-servant. | and "vant" is just from haskell-servant. | ||
Revision as of 21:04, 6 August 2020
Précis
Redvant , or 'dcms<' (dcms-bra), 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 as in red5 or the parfume.
and "vant" is just from haskell-servant.
Stands for otherwise unnamed consumer product development flows in my public job shop in or 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 and Entity Framework apps such as WINS3FS.
Ideally, the layers of any mediating app between these endpoints would be developed from first DDD principles. Practically, back filled adherence to DDD principles while integrating arbitrary predeveloped elements must suffice.
Deliverables
- ISIS Common DCMS platform builds for
The SB base app, sufficient to establish reusable baseline and collect AKPERSONs.
- Jitsi adapted to DS
- established dcms< (private) git baseline
- stable production level live and AC SPAs
- ISIS Common DS platform builds for
GT2, TASKPM, and WINS3FS apps, (the last .net EF not ISIS) 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) (alt-rooted).
