Expertise
PHP developer — since 2008
I have written PHP since 2008, and the first decision on a project is not the framework: it is where the business rule will live. Laravel, Symfony and CodeIgniter come after that decision.
- years
- 18
Me in the PHP ecosystem
Build a project in the reverse order and the business rule scatters across the application — which is exactly where maintenance cost begins. That is why one question sits at the centre of my work as a PHP developer: where will the business rule live? The framework, the directory layout and the test surface all come after that answer.
When I take on new work I do not pick a framework first. I first decide whether the work runs synchronously or asynchronously; then I look at the tools the team already knows, the time given to the MVP and the product’s own needs. Performance comes last on that list, because when I measured it, the gap between frameworks closes as soon as the request does real work. The same measure holds in inherited codebases: the cost of a change has to stay smaller than the relief it brings.
I have worked on Laravel, Symfony and CodeIgniter, both on work I started and on codebases I inherited. Laravel has its own page; this one covers the language itself. Microservice boundaries, event-driven design itself and database internals I write about, with their costs, in the Engineering section.
What is PHP?
PHP is a general-purpose programming language used to write the server side of web applications. A PHP developer writes web applications, APIs and background jobs in it, and carries an application's life cycle from the framework decision to testing and maintenance.
What do I do with PHP?
As a PHP developer I write invoicing and payment flows, asynchronous jobs that consume from queues, and applications with or without a framework. I have worked on Laravel, Symfony and CodeIgniter, both on codebases I started and ones I inherited; at the centre of the work is the question of where the business rule will live.
Recent writing in this area
- Blog
PHP 8.6 is on the way: the language's steady evolution
Before PHP 8.6 ships: why predictable annual releases and 'boring' versions of a mature language are actually good news.
- Blog
PHP 7.1 to 8.2: The Real Bill for a Deferred Upgrade
Moving a PHP app I maintain from 7.1 to 8.2 was proposed in 2023 and done in 2024. The most expensive line item on the bill wasn't where I expected.
- Blog
18,750 req/s: precise, repeated, and three times wrong
Two phases of the same run measured the same service three times apart. What caught the wrong one was not a better statistic but a second method.
Measurements in this area
One core carries 14,330 OAuth2 requests in Go and 5,152 in PHP-FPM
The same API verifies an RS256 bearer token on every request and then reads or writes one row in PostgreSQL — on one, two and four cores, how much mixed traffic does it carry in Go, PHP-FPM and FrankenPHP worker mode?
Finding
On four cores Go carried 57,321 mixed requests a second, FrankenPHP 25,659 and php-fpm 20,606 — 14,330, 6,415 and 5,152 per core. The number that goes into a capacity plan is not that one but application CPU per request: 66.8, 110.7 and 187.7 microseconds. At saturation FrankenPHP uses only 2.84 of its four cores, against Go's 3.83 and php-fpm's 3.87. The database is not the constraint: on the same four cores PostgreSQL alone writes 68,212 rows a second, above the mixed ceiling of the fastest candidate.
measured 62 days ago
Technologies I pair it with
-
Laravel
The framework I reach for first where business rules and money move.
-
Symfony
My pick on projects assembled component by component, with sharp boundaries.
-
CodeIgniter
The lightweight framework I meet both on greenfield work and in codebases I inherit.
-
Composer
Dependency management; where I stopped downloading library zips in 2014.
-
PHPUnit
The base of the testing side; still what I meet in older codebases.
-
Pest
The testing surface I reach for on new projects.
-
Redis
Cache, session and queue store.
-
MySQL
Primary relational store.
-
RabbitMQ
Where billing left the synchronous path.
Questions in this area
Frequently asked
10 questions
-
How long have you worked with PHP?
Since 2008 — 18 years.
-
Which PHP frameworks do you use?
My depth is in Laravel, and the archive carries version and migration notes starting from Laravel 4. But Laravel is not my only framework — I have written Symfony and CodeIgniter both on work I started from scratch and in codebases I inherited.
-
Do you write PHP without a framework?
Yes. I have written packages that stand on their own — from a router to a PSR-11 container — without leaning on a framework; all of them MIT-licensed on Packagist. Writing PHP without a framework is also the shortest way to learn what the framework has been doing for you.
-
How do you pick a PHP framework for a project?
Three parameters decide it: the time given to the MVP, the tools the developers on the team already know and the product's own requirements. Performance is usually the weakest argument in that decision — when I measured it, the gap between frameworks closes as soon as the request does real work.
-
How do you start a new PHP project?
Not by picking a framework. First I decide whether the work runs synchronously or asynchronously. That single decision fixes the queue, the error contract and the idempotency requirement together, which makes it the most expensive one to change later.
-
Do you do architecture work as well?
Yes, but not on this page. This surface stays at application level; the architectural decisions themselves — with their costs — go in the Engineering section.
-
What does a PHP developer do?
A PHP developer writes web applications, APIs and background jobs on the server side. For me that means placing the business rule inside the application, deciding on the framework, setting up the queue and the test surface, and improving inherited code without breaking it.
-
Where do you start in an inherited PHP codebase?
Not with a rewrite, but with understanding the behaviour: where each rule sits, which side effect belongs to which request, how far the surface protected by tests reaches. An improvement made before those are clear risks breaking a working system invisibly. Then I widen the test surface; version and dependency cleanup comes last.
-
How do you set up tests in PHP projects?
On three surfaces. The business rule is tested directly, without reaching the outside world; outer boundaries such as the payment provider, the queue and third-party services are imitated; and the flow runs end to end once, along the path a request enters and a result leaves by. I use Pest on new projects and PHPUnit in older codebases.
-
Which tools do you work with in PHP?
Composer for dependency management, PHPUnit and Pest for testing, Redis for cache and queues, MySQL as the primary relational store, and RabbitMQ where billing left the synchronous path.
Let us work together
If you have work in this ecosystem, tell me what you are building and we will talk about how to build it.