In the previous topics, we explored the Queue API and the Batch API. Both allow us to process work safely and at scale. Now we move to another core backend mechanism in Drupal: the Cron API.

In the previous topic, we explored the Queue API, which allows background processing through cron. Now we move to another powerful processing system in Drupal: the Batch API.

In real Drupal applications, not every task should run immediately during a page request. Some operations are:

In the previous topic, we worked with the Entity API and performed CRUD operations. Now we go one layer deeper into Drupal’s internal architecture: the Typed Data API.

Drupal is built around entities. Content, users, taxonomy terms, files, and custom data are all stored and managed as entities.