Data Export from Web Applications: Turnkey Implementation

According to Article 20 of the GDPR, each data subject has the right to receive their personal data in a structured, commonly used, and machine-readable format.

But in practice, exporting 500,000 rows often crashes the server: a 30-second timeout and a 502 Bad Gateway. The cause is synchronous architecture and PHP limits. We solve this at the infrastructure level: asynchronous generation via queues, streaming writes to S3, and temporary signed URLs. Requirements under GDPR (Article 20) mandate providing user personal data in a machine-readable format — we implement export turnkey. Contact us for an assessment of your project.

Problems We Solve

• N+1 queries during data export: when exporting orders with items, each database query spawns new ones — for 10,000 orders that's 10,001 queries. We use lazy loading via lazy(200) and eager loading of relationships.
• Timeouts and memory exhaustion with synchronous exports >100,000 rows: the PHP script hits memory_limit and max_execution_time. Our solution is asynchronous processing via queues with a timeout of 600 seconds.
• Hydration mismatch during SSR: if export data is embedded on the frontend, React/Nuxt can desynchronize. We export everything via API with unique IDs.

Why Asynchronous Export Is Better for Large Data

Synchronous export works only for small volumes (<10k rows). As data grows, it leads to interface blocking and connection drops. An asynchronous scheme with a queue and notifications removes load from the HTTP worker and scales horizontally. When one client generates a report of 200k rows, others continue working without delays.

A typical example: a client requested an export of 150,000 orders to Excel. Initially, the developer wrote a synchronous script — at 40 seconds, PHP crashed due to memory_limit. After switching to a queue, generation took 2 minutes, and the user received an email with a link without any blocking.

[User request] → [Create ExportJob record] → [Queue Worker]
                                                     ↓
                                              [Generate files]
                                                     ↓
                                          [Upload to S3 (zip)]
                                                     ↓
                                         [Email with download link]
                                          (signed URL, 7 days TTL)

How We Do It: Laravel Implementation

We use Laravel with PHP 8.3+ for the backend. The key pattern is the DataExportService, which queues a job. The ExportUserDataJob worker generates profile (JSON), orders (CSV with BOM), and messages (JSON) files, then packages them into a ZIP for S3 upload.

class DataExportService
{
    public function exportUserData(User $user): Export
    {
        $export = Export::create([
            'user_id'    => $user->id,
            'status'     => 'pending',
            'expires_at' => now()->addDays(7),
        ]);

        ExportUserDataJob::dispatch($user, $export);

        return $export;
    }
}

class ExportUserDataJob implements ShouldQueue
{
    public int $timeout = 600;

    public function __construct(private User $user, private Export $export) {}

    public function handle(): void
    {
        $this->export->update(['status' => 'processing']);

        $tempDir = sys_get_temp_dir() . '/export_' . $this->export->id;
        mkdir($tempDir, 0777, true);

        try {
            // Профиль
            file_put_contents(
                "$tempDir/profile.json",
                json_encode($this->exportProfile(), JSON_UNESCAPED_UNICODE | JSON_PRETTY_PRINT)
            );

            // Заказы
            $this->exportOrders("$tempDir/orders.csv");

            // Сообщения
            $this->exportMessages("$tempDir/messages.json");

            // Создать ZIP
            $zipPath = sys_get_temp_dir() . "/export_{$this->export->id}.zip";
            $zip = new ZipArchive();
            $zip->open($zipPath, ZipArchive::CREATE);

            foreach (glob("$tempDir/*") as $file) {
                $zip->addFile($file, basename($file));
            }
            $zip->close();

            // Загрузить в S3
            $s3Key = "exports/{$this->user->id}/{$this->export->id}/data.zip";
            Storage::disk('s3')->put($s3Key, file_get_contents($zipPath));

            $this->export->update([
                'status'   => 'ready',
                's3_key'   => $s3Key,
            ]);

            $this->user->notify(new ExportReadyNotification($this->export));

        } finally {
            exec("rm -rf {$tempDir}");
            if (file_exists($zipPath ?? '')) unlink($zipPath);
        }
    }

    private function exportProfile(): array
    {
        return [
            'id'         => $this->user->id,
            'name'       => $this->user->name,
            'email'      => $this->user->email,
            'created_at' => $this->user->created_at->toIso8601String(),
            'profile'    => $this->user->profile?->toArray(),
        ];
    }

    private function exportOrders(string $path): void
    {
        $handle = fopen($path, 'w');
        fprintf($handle, chr(0xEF) . chr(0xBB) . chr(0xBF));  // UTF-8 BOM
        fputcsv($handle, ['Номер', 'Дата', 'Сумма', 'Статус', 'Позиции'], ';');

        $this->user->orders()->with('items')->lazy(200)->each(function (Order $order) use ($handle) {
            $items = $order->items->map(fn($i) => "{$i->name} x{$i->quantity}")->join(', ');
            fputcsv($handle, [
                $order->number,
                $order->created_at->format('d.m.Y H:i'),
                number_format($order->total, 2),
                $order->status,
                $items,
            ], ';');
        });

        fclose($handle);
    }

    private function exportMessages(string $path): void
    {
        $messages = $this->user->messages()
            ->select('id', 'subject', 'body', 'created_at')
            ->get()
            ->map(fn($m) => [
                'id'      => $m->id,
                'subject' => $m->subject,
                'body'    => strip_tags($m->body),
                'date'    => $m->created_at->toIso8601String(),
            ]);

        file_put_contents($path, json_encode($messages, JSON_UNESCAPED_UNICODE | JSON_PRETTY_PRINT));
    }

    public function failed(\Throwable $e): void
    {
        $this->export->update(['status' => 'failed']);
        Log::error('Export failed', ['export_id' => $this->export->id, 'error' => $e->getMessage()]);
    }
}

How Signed URLs Work for Download

To avoid storing archives indefinitely, we use temporary S3 links with a 15-minute TTL. The user receives an email with a unique link that points directly to S3 — bypassing our server.

public function download(Export $export): RedirectResponse
{
    $this->authorize('download', $export);

    if ($export->status !== 'ready' || $export->expires_at->isPast()) {
        abort(410, 'Экспорт недоступен или устарел');
    }

    $url = Storage::disk('s3')->temporaryUrl($export->s3_key, now()->addMinutes(15));

    return redirect()->away($url);
}

Choosing the Right Export Format

The format depends on the purpose: JSON for API and GDPR extraction, CSV with BOM for tables and Excel, XLSX with formatting for accounting, XML for B2B integrations. If multiple files are needed, we use ZIP.

Our Process

1. Analysis — we study the data structure, volumes, and format requirements.
2. Design — select the tech stack (queue, storage), design the export database schema.
3. Development — write services, workers, controllers, and tests.
4. Testing — load testing with real volumes, timeout checks.
5. Deployment — configure queues (Redis, SQS), S3, clean-up crons.
6. Documentation — hand over architectural docs and instructions.

What's Included

• Architectural documentation with data flow descriptions.
• Source code with comments and strict typing.
• Deployment instructions with examples of queue and S3 configuration.
• Training for support staff.
• 3-month warranty for uninterrupted operation.

Timeline and Pricing

Basic user data export (JSON + CSV in ZIP): 2–3 days. With queue, S3, and email notification: 3–4 days. GDPR-compliant export of all personal data: 4–5 days. Pricing is determined individually based on data volumes and number of formats. Our team has over 10 years of experience and has completed 40+ data export projects. Order an export for your project — get a free consultation and estimate within one day.

Contact us to discuss your project and receive an accurate estimate.

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.