Redvant: Difference between revisions
No edit summary |
|||
| Line 8: | Line 8: | ||
'''Redvant''' is react, redux FE with | '''Redvant''' is react, redux FE with | ||
[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 as a focus/incubator for DCMS and tl:dr/Jackson. | backend as a focus/incubator for DCMS and tl:dr/Jackson. | ||
This is a names for systems and consumer product flows in my job shop and not products or even components. | |||
{{TOCright}} | {{TOCright}} | ||
Revision as of 03:11, 18 December 2018
Précis
Redvant is react, redux FE with servant backend as a focus/incubator for DCMS and tl:dr/Jackson.
This is a names for systems and consumer product flows in my 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.
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).
