Redvant: Difference between revisions
No edit summary |
No edit summary |
||
Line 18: | Line 18: | ||
</blockquote> | </blockquote> | ||
There is an intent to join it with DDD product line engineering and that is the 'redvant' / 'redvantis' distinction. | |||
Revision as of 12:54, 27 August 2021
Précis
Redvant , or 'dcms<' (dcms-bra), is an omnibus designation for assorted software including principally react and servant and ultimately to be packages as uniform support of the sameboat and tl:dr[AK] applications.
"red" could be
react, redux, redis, or just plain red, a simple name as in red5, the parfume, riding hood, etc..
and "vant" is just from haskell-servant.
There is an intent to join it with DDD product line engineering and that is the 'redvant' / 'redvantis' distinction.
Story
Red<thing> is a name for a dev workflow defined by an implementation path from front end thru DCMS middleware, to arbitrary backend function and DCP agents;
Redvant is rapid prototyping and React oriented but its work product is not disposable. Rather it remains the simple, easily mutable, and generally feature poor base of a product line entry.
Redvantis is an optional layer using the Apache ISIS and Django Oscar packages as the front end and middle ware layers over the domain ledger, supporting DDD app development.
In an actual product line actual entry could be Redvant Expo, Redvant Native, Redvantis alone or Redvantis behind Redvant Native, where the first Redvant screens precede the Redvantis ones.
Sonstiges
Commonalities
The sb-sff common Redvis reusable base with ...
- DS SSO, messaging, and DCMS API setup for product families.
- Jitsi adapted to DS, default in sb-sff, optional otherwise.
Deliverables
- tl;dr product line engineering cases for GT2, TASKPM, and YAS3FS.
- stable production level Ft and AC SPAs