anchor.diff:  = detailed
  -:author: 
  -:revnumber: 
  +:author:
  +:revnumber:
   :revdate: 2016/03/17 20:48
   :relfileprefix: ../../../
   :imagesdir: ../../..
  
positive.code: 
  NOTE: Definition notations:
  
  *  Normal is clearly/no doubt in the definition. 
  *  *Bold* is keywork.
  *  _Italic_ is example
  *  +++<u>Underling</u>+++ is doubt
  
negative.code: .  Flat table problem: Because ES is a big table by nature, with component set is a row. It’s as efficient even less than a big table, which form the flat table problem as seen in many indexed base database. Tree, Graph and other data structure will almost immediately break the ES contract!!
  .  Observation problem: As update beat over listening method, ES restrict the observation methods a lot.
  .  Sercurity problem : No encapsulation, kind of no private POJO mean no java power in protecting data, a lot of security holes! ES implementations and COP forget all about sercurity danger as Component contracted to be processed by Processor but not hiding its content.
  .  Scale : In theory, ES should scale well..!!! But read this carefully or mislead it, enterprise system need much more than just a way to orginize your data!!!
  
  
  [TIP]
  