Redvant: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
(→Spec) |
(→Story) |
||
| Line 9: | Line 9: | ||
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. | ||
Ideally, the layers of the mediating app between these endpoints would be developed from first DDD | 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. | Practically, much prexisting functionality can be exposed thru this channel, regardless of it's origin if its function can be abstracted. | ||
Revision as of 12:53, 28 October 2018
Précis
Redvant is react, redux, with servant which is mainly a design package package for my tl:dr line of apps and a catch all for related stuff in early stages of my consumer and system app product development.
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
- Common X-Platform app builds
- Establish DCMS baseline
