13 posts filed under php.
Installing a database driver in PHP used to mean phpize, a compiler, and a prayer; the MongrelDB PHP client is pure PHP installed with one Composer command, and this post explains why that is still a feature in 2026.
The PHP runtime argument is real for your application code, but a database client that speaks plain HTTP to a daemon does not participate in it, and here is the code to prove it.
A huge share of the web still runs on hosting plans where you cannot compile anything, and a database client that ships as plain Composer files is the difference between deploying there and telling the customer to move.
The MongrelDB PHP client mirrors the daemon's two auth modes with one constructor argument each, and anything more exotic, from per-request token vending to signing proxies, goes behind a one-method TransportInterface you control.
The MongrelDB PHP client substitutes malformed UTF-8 instead of rejecting the whole request, and reserves hard errors for values like INF, NAN, and recursive structures that genuinely have no JSON representation.
The MongrelDB PHP client treats schema as typed data instead of SQL strings, so the same call that creates a table can be paired with a catalog read that proves the server stored what you think it stored.
The MongrelDB PHP client's fluent query builder names the index family in each condition instead of generating SQL for a planner to second-guess, so the index choice you made at schema time is the one that executes.
The MongrelDB PHP client stages multi-row writes locally, commits them as one atomic HTTP batch, and dedupes retries with storage-layer idempotency keys, so a timed-out request is safe to replay without building an outbox.
The MongrelDB PHP client maps HTTP status codes to a small typed exception hierarchy, so a 401 is an AuthException, a 409 is a ConstraintException carrying the server's error code and the failing operation index, and your catch blocks read like the failure modes they handle.
The MongrelDB PHP client hides all of HTTP behind a one-method TransportInterface, ships cURL as the default with a stream fallback, and lets you inject a fake for tests or a PSR-18 bridge for Guzzle without touching application code.
The MongrelDB PHP client opts into PHP 8.5's persistent cURL share handles to carry DNS, TLS sessions, and the connection pool across FPM requests, and silently falls back to per-request pooling on 8.4.
PHP 8.4 is the floor of the pure PHP client, and PHP 8.5, released in November 2025, is where the language gives us enough to stop writing workarounds for cURL and readonly cloning.
Install the MongrelDB PHP 8.4+ client with Composer and connect to mongreldb-server over HTTP without compiling a custom PHP extension.
