Glossary

This glossary covers terms that come up repeatedly in the Zend Framework Book chapters, guides, and topic hubs. Definitions are written for working developers rather than academic audiences.

A

Autoloading

The mechanism by which PHP automatically loads class files when they are first referenced, eliminating the need for manual require or include statements. PSR-4 autoloading via Composer is the modern standard, replacing the older PSR-0 and Zend Framework 1 autoloader patterns.

B

Bootstrap

The initialisation phase of a Zend Framework application where resources such as the database adapter, view renderer, router, and plugin broker are configured. Zend_Application standardises this process through resource methods and configuration files.

C

Caching Strategy

A deliberate approach to storing frequently accessed data or computed results closer to the consumer, reducing repeated database queries, file reads, or expensive computations. Common strategies in PHP include opcode caching, object caching with Memcached or Redis, and HTTP-level cache headers.

Controller Action

A public method within a controller class that handles a specific route or user interaction. Each action typically gathers request data, delegates to models or services, and prepares variables for the view layer.

D

Data Mapper

A persistence pattern where a dedicated mapper class handles the translation between domain objects and database rows. This decouples business entities from storage details, making the domain model easier to test and refactor.

Dispatch Loop

The iterative process within the front controller where the router determines which controller and action to invoke, the dispatcher executes them, and the cycle may repeat if a forward or redirect is triggered before the final response is sent.

Related: Application Architecture

Domain Model

A structural representation of the business logic and data relationships within an application. In PHP frameworks, domain models encapsulate entity behaviour, validation rules, and business constraints independently of the persistence layer.

F

Front Controller

A design pattern where a single entry point handles all incoming HTTP requests, routing them to the appropriate controller and action. In Zend Framework 1, Zend_Controller_Front serves this role, managing the dispatch loop, plugins, and the router.

Related: Application Architecture

L

Layout System

A two-step rendering approach where individual view scripts are wrapped within a shared layout template. Zend_Layout provides this in Zend Framework 1, separating page-specific content from the surrounding chrome of headers, navigation, and footers.

Related: Setting the Design

M

Migration Path

A planned sequence of steps for moving an application from one framework version, language version, or architecture pattern to another. For Zend Framework projects, the primary migration path today leads to Laminas, the official successor project.

MVC Pattern

Model-View-Controller is an architectural pattern that separates an application into three interconnected layers. The model manages data and business rules, the view handles presentation, and the controller mediates input and coordinates between the two.

P

Persistence Layer

The portion of an application responsible for storing and retrieving data, typically through database queries, file systems, or external services. Clean separation between the persistence layer and domain logic is a hallmark of maintainable PHP architecture.

R

Request Lifecycle

The complete journey of an HTTP request through a web application, from the initial server receipt through routing, dispatching, controller execution, view rendering, and the final response. Understanding this lifecycle is fundamental to debugging and performance work.

V

View Helper

A reusable function or class method available within view templates that encapsulates common rendering tasks such as formatting dates, generating URLs, building form elements, or rendering navigation structures.

Related: Setting the Design

Virtual Host

An Apache HTTP Server configuration that allows multiple domain names to be served from a single server instance. Name-based virtual hosts are commonly used in local PHP development to map project-specific domains to different document roots.