Drupal Entity API

When to use

• The user needs a Drupal configuration entity to store admin-defined settings that ship as exportable config.
• The user wants to define a custom Drupal content entity type to store repeatable, fieldable data.
• The user wants to load, query, save, or delete Drupal entities through the entity type manager and storage.

When NOT to use

• Do not create and query a raw custom database table when a content entity would model the same fieldable data.
• Do not define an entity type for one flat setting; use simple configuration (config.factory) instead.

Core guidance