anchor.diff:  .  Regular workload : software that run at regular rate, kind of ballance trade off between performance and complexity
   .  Simple dataflow: the flow of the data is easy to watch, inspect, start stop, manipulate. As the root reason for regular workload!
   
  -```
  +
   Ideas similarities here actually is resulted from with decades of history of revolving of the paradigm. That's why you will see the same concepts of Entity system appear every where from a database to a repository. Of course because it have the same root.Check Pros and Cons chapter for full, detailed idea and design goals and successes.
  -```
  +
   
   
   == Terms
  
positive.code: 
  === System ~ Processor?
  
  ```
    In a pure ES, this is not a thing, really. Some implementations force this on you because they couldn’t think how to do the ES job efficiently… but it’s still not a thing. All of your code that isn’t an ES is a "`system`", technically.
  ```
  
  System = everything that isn’t an Entity or a Component but uses Entities and Components.
  
  
negative.code: From more 'open' perspective the core elements can be viewed as, but remember the name as a noun can be mislead:
  _This resulted as a dicussion of @pspeed and toolforger, eventually is form a skeptical question, it's really interesting by how we all see this problem confused at first!!_
  
  ]
  Entity -> ID. It just binds the components together, in the sense that there is one function that creates a bunch of components with the same ID, and one function to destroy all components for an ID. An entity is the set of objects that have the same ID, entities don’t exist as coherent objects inside the code.
  
  Component -> Facet. A position is a facet of an entity, as its velocity, its health, its armor, its whatever. If entities were Java objects, facets would be groups of interrelated properties.
  
  System -> Processor. A function that operates on a slice of components.
  
  This often result in mislead skepticism about the design. So get back to read it carefully one more time and some gotchas and practical wisdom below.
  
  
  