Reference architectures

Zapthink remind us of the value of reference architectures.

The Ujuzi take (with apologies):

  1. build on a pre-existing reference architecture where possible (this is the standing on the shoulders of giants bit)
  2. if  you are committed to a vendor’s product, decide how deeply you are prepared to entrench it in your architecture and then build on their best practices for the chosen bits
  3. maintain a register of lessons learned (and solutions) as you go through projects
  4. document antipatterns and how to avoid them
  5. document new patterns and how to apply them
  6. document what doesn’t work as advertised – whether it is a vendor product capability or just an architectural approach
  7. PoC, PoC, PoC