Difference between revisions of "Redvant"

From Cibernética Americana
(Story)
Line 14: Line 14:
 
  react, redux, redis, or just plain red, a simple name.
 
  react, redux, redis, or just plain red, a simple name.
 
</blockquote>  
 
</blockquote>  
 +
and "vant" is just from haskell-servant.
 
</blockquote>  
 
</blockquote>  
  
This is a name for systems and consumer product development flows in my public job shop and not products or even components.
+
Stands for otherwise unnamed consumer product development flows in my public job shop outside of the DDD process.
  
 
{{TOCright}}
 
{{TOCright}}
Line 22: Line 23:
 
= Story =
 
= 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.
+
Redvant is a name for a dev workflow defined by an implementation path from front end thru DCMS middleware, to arbitrary domain space function, but particularly Apache ISIS based end consumer apps such as GT2 and TASKPM.
  
Ideally, the layers of the mediating app between these endpoints would be developed from first DDD principles.
+
Ideally, the layers of any mediating app between these endpoints would be developed from first DDD principles. Practically, besides the GT2 and TASKPM exemplars, just doing it and getting it done to a useable state is the good here.
'
 
Practically, some preexisting functionality may be lumped under this rubric, regardless of its provenance.
 
  
 
== Residue/Result ==
 
== Residue/Result ==

Revision as of 10:15, 19 April 2019