Redvant: Difference between revisions
No edit summary |
(→Story) |
||
| Line 25: | Line 25: | ||
Ideally, the layers of the mediating app between these endpoints would be developed from first DDD principles. | Ideally, the layers of the mediating app between these endpoints would be developed from first DDD principles. | ||
' | |||
Practically, | Practically, some preexisting functionality may be lumped under this rubric, regardless of its provenance. | ||
== Residue/Result == | == Residue/Result == | ||
Revision as of 12:32, 4 March 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.
This is a name for systems and consumer product development flows in my public job shop and not products or even components.
Story
Redvant is a name for a software development architecture/pipeline defined by main implementation elements of its endpoints, where DCMS although middleware, is considered an endpoint.
Ideally, the layers of the mediating app between these endpoints would be developed from first DDD principles. ' Practically, some preexisting functionality may be lumped under this rubric, regardless of its provenance.
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).
