Archives de la catégorie design

Java Keystore Certificate Public Private Key

A few articles/posts on the subject :

http://javarevisited.blogspot.fr/2012/09/difference-between-truststore-vs-keyStore-Java-SSL.html

http://superuser.com/questions/620121/what-is-the-difference-between-a-certificate-and-a-key-with-respect-to-ssl

Pas de commentaire

Hierarchical Enum in Java

Note that post was written in 2010 : http://alexradzin.blogspot.fr/2010/10/hierarchical-structures-with-java-enums_05.html

Might be worth to re-explore the idea with new Java versions…

Pas de commentaire

JSON LD : linking data through the web…

Places to start with…

http://manu.sporny.org/2014/json-ld-origins-2/

http://www.w3.org/TR/json-ld/#iris

Pas de commentaire

DOCKER – or app in a box / box handling environment

Start here : https://www.docker.com/whatisdocker/

Pas de commentaire

parallel computation : FORK JOIN – ciLk …

  • http://en.wikipedia.org/wiki/Cilk
  • http://coopsoft.com/ar/Calamity2Article.html
  • http://zeroturnaround.com/rebellabs/is-java-8-the-fastest-jvm-ever-performance-benchmarking-of-fork-join/

Pas de commentaire

DDD & CQRS sample project

To keep an eye on :

https://code.google.com/p/ddd-cqrs-sample/

and its [Architecture and design visual map] viewer

 

Pas de commentaire

keeping a pointer to this article : DDDD: Eric Evans Interviews Greg Young

http://blog.jonathanoliver.com/dddd-eric-evans-interviews-greg-young/

Note : DDDD = distributed DDD

Pas de commentaire

UML : « Keep your UML sources »

Pas de commentaire

Functional Reactive Programming – data streams are talking to you!

follow the link… https://gist.github.com/staltz/868e7e9bc2a7b8c1f754

Pas de commentaire

DDD : (Sub)Domain/Model/Bounded Context – opinionated interesting article

In short :  ideally a bounded context is the model of a sub-domain but this cannot always apply when for instance a technical requirement for a sub-domain conceptually requires a bounded context for itself (the provided example was a full-text search feature in a document management domain).

Summary

A sub-domain delimits a domain and exists within the problem space. A bounded context delimits the domain model and exists within the solution space. The ideal is full alignment between a sub-domain and a bounded context, however in practice a degree of flexibility must be accepted in this regard. Furthermore, just as the bounded context is guided by a sub-domain, a sub-domain is, in turn ,guided by a bounded context as part of the model exploration whirlpool.

source :  http://gorodinski.com/blog/2013/04/29/sub-domains-and-bounded-contexts-in-domain-driven-design-ddd/

Pas de commentaire