Entity component system introduction
The Entities package uses the entity component system (ECS) architecture to organize code and data for some of its processes. An entity is a unique identifier, like a lightweight unmanaged alternative to a GameObject. An entity acts as an ID associated with individual components that contain data about the entity. Unlike types that inherit from MonoBehaviour, entities contain no code, or data: they're a reference to units of data that the systems you create process.
The following diagram illustrates how entities, components, and systems work together:

In this diagram, a system reads Speed and Direction components, multiplies them and then updates the corresponding Position components.
The fact that entities A and B have a Renderer
component but entity C doesn't makes no difference to the system, because the system has no knowledge of Renderer
components.
You can set up a system so that it requires a Renderer
component, in which case, the system ignores the components of entity C. Alternatively, you can set up a system to exclude entities with Renderer
components, which then ignores the components of entities A and B.
The diagram also illustrates the concept of an archetype, which is a unique combination of component types.
Additional resources
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.