---
title: "CakePHP"
description: "CakePHP is a mature open-source PHP framework built on MVC and convention over configuration. Learn its ORM, bake scaffolding and typical use cases."
url: "https://nodea.io/en/glossary/cakephp"
lang: "en"
updated: "2026-07-13"
---

# CakePHP

> CakePHP is a long-established open-source PHP framework that pairs the MVC pattern with strict naming conventions, a built-in ORM and code-generation tooling for rapid CRUD development.

**CakePHP** is an open-source web application [framework](https://nodea.io/en/glossary/framework) for [PHP](https://nodea.io/en/glossary/php), first released in 2005 and still actively maintained, making it one of the longest-lived projects in the PHP ecosystem. Its design rests on two pillars: the MVC (Model–View–Controller) pattern and the "convention over configuration" philosophy — follow the prescribed naming of tables, classes and folders, and the framework wires everything together with almost no configuration files.

## How CakePHP works

The framework ships with its own ORM built around Table and Entity classes. Point it at a relational database — MariaDB/[MySQL](https://nodea.io/en/glossary/mysql), PostgreSQL or SQLite — and it infers associations from naming conventions: an *articles* table maps to ArticlesTable and Article entities automatically. The bundled *bake* console command takes this further, generating complete CRUD scaffolding (models, controllers, templates) directly from an existing database schema.

Beyond the ORM, CakePHP provides PSR-7 compatible middleware, form validation, authentication and authorization plugins, database migrations and PHPUnit-based testing. Security features are enabled by default rather than opt-in: parameterised queries against SQL injection, CSRF tokens, output escaping against XSS and protection from mass-assignment of request data.

## Practical use cases

CakePHP excels where an application is fundamentally CRUD-shaped: admin panels, booking and inventory systems, intranets, membership portals and JSON APIs backing mobile apps. Because conventions leave little room for stylistic drift, large teams maintaining a codebase for years tend to appreciate its predictability; conversely, developers wanting maximum flexibility often prefer [Symfony](https://nodea.io/en/glossary/symfony) components or Laravel's larger package ecosystem.

Hosting requirements are unremarkable: a current PHP version with the intl and mbstring extensions plus a relational database, which any standard shared hosting plan or VPS provides. A significant amount of legacy CakePHP 2.x and 3.x code still runs in production worldwide, so the framework is also a frequent subject of maintenance and upgrade projects — the official upgrade tooling automates a large part of moving between major versions.

### How does CakePHP compare to Laravel or Symfony?

All three are MVC frameworks for PHP. CakePHP enforces conventions most strictly and generates CRUD code fastest with its bake tool; Laravel offers the largest ecosystem and developer-experience features; Symfony provides the most granular, component-based architecture. The choice usually comes down to team experience and ecosystem needs.

## Related

- [PHP](https://nodea.io/en/glossary/php)
- [Framework](https://nodea.io/en/glossary/framework)
- [Laravel](https://nodea.io/en/glossary/laravel)
- [Symfony](https://nodea.io/en/glossary/symfony)
- [MySQL](https://nodea.io/en/glossary/mysql)

---

Languages: [pl](https://nodea.pl/pl/slownik-pojec/cakephp.md)  
Site index: [llms.txt](https://nodea.io/en/llms.txt)