Native PHP Backend: Full Control Without Frameworks

Native PHP Backend: Full Control and Flexibility

Let's start with a real scenario: a client comes to us with a legacy project running on an old PHP version that can no longer handle the load. Recently we audited such a project on PHP 5.6: response times of 200 ms, frequent N+1 queries, and a struggling shared hosting environment. We rewrote the key modules in native PHP 8.x — response times dropped to 40 ms and hosting costs fell by 30%. A framework couldn't be used because of shared hosting constraints and the high cost of a full rewrite. Our solution was native PHP with typed properties, attributes, and readonly classes. We deliver a turnkey backend, preserving full control and minimizing dependencies. With 10+ years of experience, certified engineers, and over 40 completed projects, we guarantee results. Native code can be faster due to the absence of overhead. Contact us for a free audit of your project.

Why Choose Native PHP Without a Framework?

For projects with up to 15–20 endpoints and simple logic, a native approach delivers up to 30% better performance compared to Laravel or Symfony — thanks to zero overhead. You select exactly which libraries to include: FastRoute for routing, php-di for dependency injection, Phinx for migrations. Nothing unnecessary. Budget savings can reach 20% because there are no framework license costs or bloated dependencies. For example, a typical small API (10 endpoints) costs between $5,000 and $10,000.

What Problems Do We Solve?

• N+1 queries in PDO. We implement a Repository pattern with data aggregation via JOINs instead of separate queries. This reduces the number of database queries by a factor of 10.
• Security. We use PDO prepared statements, server-side validation, and JWT with a limited TTL — all written manually, without framework 'magic'. In one project, we uncovered an XSS vulnerability that a framework would have missed.
• Performance. We minimize class autoloading, enable OPCache, and profile with Xdebug. Load testing is mandatory. In one case, throughput increased from 500 to 2000 RPS.

How Do We Implement Authentication and Security?

Authentication is built on JWT with a short TTL (15 minutes). The refresh token is stored in an http-only cookie. Token validation and parsing can be written in just 20 lines of code without any library. For production, we rely on firebase/php-jwt, but a custom solution works for basic needs. CORS policies and CSRF protection are configured in middleware.

How Does PDO Improve Performance?

PDO with prepared statements not only protects against SQL injection but also allows repeated execution of the same query with different parameters. We use a Singleton connection pool, shaving 5–10 ms off each connection setup.

Native PHP vs Frameworks: A Comparison

Typical Phases and Timelines

How We Do It: Stack and Implementation

We use PHP 8.x, PostgreSQL 15, Nginx in Docker. Example entry point:

<?php
// public/index.php

declare(strict_types=1);

require_once __DIR__ . '/../vendor/autoload.php';

use App\Core\Router;
use App\Core\Request;
use App\Core\Response;
use App\Middleware\CorsMiddleware;
use App\Middleware\AuthMiddleware;

$request = Request::fromGlobals();
$router  = new Router();

require __DIR__ . '/../routes/api.php';

$middlewares = [new CorsMiddleware(), new AuthMiddleware()];
$response    = (new Pipeline($middlewares))->handle($request, fn($req) => $router->dispatch($req));
$response->send();

The router uses FastRoute — faster than alternatives:

<?php
namespace App\Core;

use FastRoute\Dispatcher;
use FastRoute\RouteCollector;
use function FastRoute\simpleDispatcher;

class Router
{
    private array $routes = [];

    public function get(string $pattern, array $handler, array $middlewares = []): void
    {
        $this->routes[] = ['GET', $pattern, $handler, $middlewares];
    }

    public function post(string $pattern, array $handler, array $middlewares = []): void
    {
        $this->routes[] = ['POST', $pattern, $handler, $middlewares];
    }

    public function dispatch(Request $request): Response
    {
        $dispatcher = simpleDispatcher(function (RouteCollector $r) {
            foreach ($this->routes as [$method, $pattern, $handler, $middlewares]) {
                $r->addRoute($method, $pattern, [$handler, $middlewares]);
            }
        });

        $info = $dispatcher->dispatch($request->method(), $request->path());

        return match ($info[0]) {
            Dispatcher::FOUND => $this->handleFound($info[1], $info[2], $request),
            Dispatcher::NOT_FOUND => Response::json(['error' => 'Not Found'], 404),
            Dispatcher::METHOD_NOT_ALLOWED => Response::json(['error' => 'Method Not Allowed'], 405),
        };
    }

    private function handleFound(array $routeInfo, array $params, Request $request): Response
    {
        [$handler, $middlewares] = $routeInfo;
        [$class, $method] = $handler;

        foreach ($middlewares as $middleware) {
            $result = app($middleware)->handle($request);
            if ($result instanceof Response) return $result;
        }

        return app($class)->$method($request, $params);
    }
}

Validation and Database Layer

A custom validator using match and attributes:

<?php
namespace App\Core;

class Validator
{
    private array $errors = [];

    public function validate(array $data, array $rules): bool
    {
        $this->errors = [];
        foreach ($rules as $field => $fieldRules) {
            foreach (explode('|', $fieldRules) as $rule) {
                $this->applyRule($data, $field, $rule);
            }
        }
        return empty($this->errors);
    }

    private function applyRule(array $data, string $field, string $rule): void
    {
        $value = $data[$field] ?? null;
        [$ruleName, $param] = array_pad(explode(':', $rule, 2), 2, null);

        match ($ruleName) {
            'required' => !isset($data[$field]) || $data[$field] === ''
                ? $this->addError($field, 'required', "Field {$field} is required")
                : null,
            'min' => is_string($value) && strlen($value) < (int) $param
                ? $this->addError($field, 'min', "Minimum {$param} characters")
                : null,
            'max' => is_string($value) && strlen($value) > (int) $param
                ? $this->addError($field, 'max', "Maximum {$param} characters")
                : null,
            'numeric' => $value !== null && !is_numeric($value)
                ? $this->addError($field, 'numeric', "Field {$field} must be numeric")
                : null,
            'email' => $value && !filter_var($value, FILTER_VALIDATE_EMAIL)
                ? $this->addError($field, 'email', 'Invalid email')
                : null,
            default => null
        };
    }

    private function addError(string $field, string $rule, string $message): void
    {
        $this->errors[$field][$rule] = $message;
    }

    public function getErrors(): array { return $this->errors; }
}

PDO connection with Singleton and a simple Query Builder for common operations:

class QueryBuilder
{
    private PDO $pdo;
    private string $table;
    private array $conditions = [];
    private array $bindings   = [];
    private ?int $limit       = null;
    private ?int $offset      = null;

    public function __construct(string $table)
    {
        $this->pdo   = Database::getInstance();
        $this->table = $table;
    }

    public function where(string $column, mixed $value): static
    {
        $placeholder = ':' . $column . count($this->bindings);
        $this->conditions[] = "{$column} = {$placeholder}";
        $this->bindings[$placeholder] = $value;
        return $this;
    }

    public function limit(int $limit): static { $this->limit = $limit; return $this; }
    public function offset(int $offset): static { $this->offset = $offset; return $this; }

    public function get(): array
    {
        $sql  = "SELECT * FROM {$this->table}";
        if ($this->conditions) {
            $sql .= ' WHERE ' . implode(' AND ', $this->conditions);
        }
        if ($this->limit !== null) $sql .= " LIMIT {$this->limit}";
        if ($this->offset !== null) $sql .= " OFFSET {$this->offset}";

        $stmt = $this->pdo->prepare($sql);
        $stmt->execute($this->bindings);
        return $stmt->fetchAll();
    }

    public function insert(array $data): int
    {
        $columns     = implode(', ', array_keys($data));
        $placeholders = implode(', ', array_map(fn($k) => ":{$k}", array_keys($data)));
        $stmt        = $this->pdo->prepare("INSERT INTO {$this->table} ({$columns}) VALUES ({$placeholders})");
        $stmt->execute($data);
        return (int) $this->pdo->lastInsertId();
    }
}

Our Work Process

1. Analysis — we review the current architecture, load, and bottlenecks.
2. Design — we agree on the database schema, routing, and middleware.
3. Implementation — we write code and cover it with unit tests (PHPUnit).
4. Testing — load and integration testing.
5. Deployment — setup CI/CD, monitoring, and documentation.

What’s Included in Our Work

• Source code with comments
• API documentation (OpenAPI)
• Database migrations (Phinx)
• Access to repository and server
• Team training (2 hours)
• One month of post-launch support

Timelines and Pricing

• Basic infrastructure (router, DI, Request/Response) — 3–7 days
• Models, PDO, Query Builder — 3–5 days
• Authentication (JWT) — 2–3 days
• Business logic — 1–3 weeks

Total: 2–5 weeks for a small API. Cost is calculated individually based on complexity. Budget savings of up to 20% are typical due to the absence of framework overhead. For a typical small API (10 endpoints), the total cost ranges from $5,000 to $10,000.

Optimal Scenarios for Native PHP

• Small API — up to 15 endpoints.
• Shared hosting — no access to Composer or frameworks.
• Legacy migration — step-by-step replacement of system parts.
• High performance — a microservice handling 1000+ RPS.

Order native PHP backend development — get a stable, framework-free architecture. Get a consultation — our engineers will help assess whether native PHP fits your project. Just write to us.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.