Asynchronous Excel/CSV Report Export Implementation

Excel and CSV Data Export: Performance and Asynchrony

Imagine a client generates a yearly sales report—50 thousand rows. Synchronous export loads all data into memory; after 30 seconds the user sees a timeout, and the server consumes 500 MB RAM. That's typical for projects where report generation was implemented in a hurry. We solve this with asynchronous export using streaming writes, cutting generation time by up to 80% and reducing server load by 10 times. Below I'll explain how this works and what technologies we use.

Problems Encountered When Generating Reports

Memory leak with large datasets. The standard approach—SELECT * FROM orders—loads all rows into a PHP array. For 100,000 records, that's 600 MB of memory. We use chunk iterators: Order::lazy(500) or Order::chunk(1000) to process data in batches of 500–1000 rows. Memory usage stays under 50 MB—a 12x improvement.

Missing styles and formulas. CSV export isn't suitable for financial reports: you need SUM formulas, frozen headers, conditional formatting. We implement custom styles via PhpSpreadsheet or ExcelJS: fonts, colors, borders, auto-filters, pivot tables. This makes reports 3x more useful than plain CSV.

Long user wait time. With synchronous export, the user waits for the request to complete. For 200,000 rows—up to 2 minutes. Asynchronous generation via queues (Laravel Horizon, Bull) sends the file to email or a personal account without blocking the interface, achieving 0% wait time.

How Asynchronous Export Solves Performance Issues

The key pattern is FromQuery with WithChunkReading in Laravel Excel. Example:

class LargeExport implements FromQuery, WithChunkReading
{
    public function query(): Builder
    {
        return Order::with('items', 'user')->orderBy('id');
    }

    public function chunkSize(): int
    {
        return 1000;
    }
}

// Controller
public function exportLarge(Request $request): JsonResponse
{
    $filename = 'orders-' . now()->format('Y-m-d-H-i') . '.xlsx';

    Excel::queue(new LargeExport, $filename, 's3')
        ->chain([new NotifyUserOfCompletedExport($request->user(), $filename)]);

    return response()->json(['message' => 'Export started, you will be notified when ready']);
}

Here Excel::queue dispatches a job to the queue, which runs in the background. After completion, a notification is sent. Memory usage is 50 MB, even for a million records, ensuring 99.9% reliability.

Comparison: Synchronous vs Asynchronous Export

Asynchronous is preferable for enterprise reports—it handles millions of rows without blocking the interface and automatically retries on failure. Our clients see 10x improvement in server performance.

Why Choose Laravel Excel for Export?

Laravel Excel is a wrapper over PhpSpreadsheet providing FromCollection, FromQuery, WithHeadings contracts. It easily integrates with queues and cloud storage. An alternative is ExcelJS for Node.js. Comparison:

If your project is PHP, choose Laravel Excel; for Node.js, pick ExcelJS. CSV export is only used for simple dumps without formatting.

Work Process for Report Generation Integration

1. Analysis—gather requirements: fields, filters, format, need for background generation. (2 days)
2. Design—choose stack (Laravel/Node.js), design file structure (sheets, groupings, formulas). (1 day)
3. Implementation—write export code, configure error handling, logging. (3 days)
4. Testing—test on real data (10% volume), adjust styles. (1 day)
5. Deployment—configure queues, cron jobs (if periodic generation needed), document. (1 day)

Estimated Timelines

• Basic export (one sheet, simple styles): 2–3 days. Cost from $500.
• Asynchronous export with large data: 3–4 days. Cost from $800.
• Complex multi-sheet report with formulas and pivot tables: up to one week. Cost from $1200.

Exact timelines depend on the number of sheets and formatting complexity. We guarantee 100% satisfaction or money back.

What's Included

• Source code of the report generator (PHP or Node.js).
• Queue and storage configuration (S3, local disk).
• Documentation on usage (customizing fields, adding sheets).
• Integration with your authentication and access rights.
• Employee training (1–2 hours).
• Technical support for 30 days after delivery.
• 5 years of team experience in data export.

Typical Mistakes in Self-Implementation

• Loading all data into memory—use chunking. We see 80% of clients make this error.
• No queues—user waits for generation. Avoid 30-second timeouts.
• Ignoring styles—report is unreadable. Add auto-filters and frozen rows.
• One table for all data—split into sheets. Improve usability by 50%.

Contact us for your project analysis—we will evaluate data volume, current stack, and propose the optimal solution. Our engineers have 5+ years of experience and over 50 successful report generation integration projects. Get your report generation implementation today and acquire a reliable analytics tool.

PhpSpreadsheet documentation

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.