Redvant: Difference between revisions
(→Précis) |
(→Story) |
||
| Line 16: | Line 16: | ||
= Story = | = Story = | ||
Redvant is a name for a software development architecture/pipeline defined by main implementation elements of its endpoints. | 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. | Ideally, the layers of the mediating app between these endpoints would be developed from first DDD principles. | ||
Revision as of 17:43, 3 February 2019
Précis
Redvant is purescript-react, redux FE with servant backend as a focus/incubator for DCMS and tl:dr/Jackson.
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, much prexisting functionality can be exposed thru this channel, regardless of it's origin if its function can be abstracted.
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).
