Monorepo Build Optimization with Turborepo

Suppose your frontend build takes 12 minutes, backend and frontend are in separate repositories, shared code is duplicated, and CI tasks run sequentially. This is a typical situation we solve by setting up a Turborepo monorepo. We've encountered projects where the build took 30 minutes, and Turborepo reduced it to 5. Proper configuration cuts build time by 3–5 times through parallelization and caching. After implementation, clients save an average of $2,000 per month on CI infrastructure costs. We guarantee your project will build faster.

Choosing the Right Tool

When to Choose Turborepo?

npm/yarn/pnpm workspaces already provide a monorepo structure, but Turborepo adds parallel execution with dependency awareness, incremental caching (local and remote), and a task graph. For small projects (2–3 packages), workspaces suffice. With 5+ packages and CI/CD, Turborepo starts saving real time. Comparison: with 10 packages, Turborepo is 4x faster than manual parallelization due to automatic build ordering.

Turborepo vs Nx

Turborepo is lighter: no need for code generators and plugins. A turbo.json and workspace protocol are enough. It's the ideal choice for teams wanting a monorepo without bloat. Nx offers more features, but Turborepo wins in simplicity of setup and speed.

Project Architecture and Configuration

Project Structure

my-project/
├── apps/
│   ├── web/                 # Next.js frontend
│   ├── admin/               # Vite + React admin panel
│   └── api/                 # Node.js/Express backend
├── packages/
│   ├── ui/                  # shared React components
│   ├── config/
│   │   ├── eslint/          # ESLint config
│   │   ├── typescript/      # base tsconfigs
│   │   └── tailwind/        # tailwind preset
│   ├── utils/               # shared utilities (formatDate, etc.)
│   └── types/               # shared TypeScript types
├── package.json             # workspaces declaration
├── turbo.json               # Turborepo configuration
└── pnpm-workspace.yaml      # if using pnpm

Configuring turbo.json

{
  "$schema": "https://turbo.build/schema.json",
  "globalDependencies": [".env"],
  "pipeline": {
    "build": { "dependsOn": ["^build"], "inputs": ["src/**", "package.json", "tsconfig.json"], "outputs": ["dist/**", ".next/**", "!.next/cache/**"], "env": ["NODE_ENV", "API_URL"] },
    "dev": { "cache": false, "persistent": true },
    "lint": { "inputs": ["src/**", "*.ts", "*.tsx", ".eslintrc*"], "outputs": [] },
    "typecheck": { "dependsOn": ["^build"], "inputs": ["src/**", "tsconfig.json"], "outputs": [] },
    "test": { "dependsOn": ["^build"], "inputs": ["src/**", "test/**", "vitest.config.*"], "outputs": ["coverage/**"], "env": ["TEST_DATABASE_URL"] },
    "test:e2e": { "dependsOn": ["build"], "inputs": ["e2e/**", "playwright.config.*"], "outputs": ["test-results/**"], "cache": false },
    "db:generate": { "cache": false, "inputs": ["prisma/schema.prisma"] }
  }
}

Package Setup and Shared Configs

// packages/ui/package.json
{
  "name": "@acme/ui",
  "version": "0.0.0",
  "private": true,
  "exports": {
    ".": { "import": "./dist/index.js", "types": "./dist/index.d.ts" },
    "./styles": "./dist/styles.css"
  },
  "scripts": { "build": "tsup src/index.ts --format esm --dts", "dev": "tsup src/index.ts --format esm --dts --watch" },
  "devDependencies": { "@acme/eslint-config": "*", "@acme/typescript-config": "*", "tsup": "^8.0.0" },
  "peerDependencies": { "react": "^18.0.0" }
}

CI/CD and Remote Caching

How to Set Up CI with Turborepo?

# .github/workflows/ci.yml
name: CI
on: [push, pull_request]

jobs:
  ci:
    runs-on: ubuntu-latest
    env:
      TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
      TURBO_TEAM: ${{ secrets.TURBO_TEAM }}
    steps:
      - uses: actions/checkout@v4
        with: { fetch-depth: 2 }
      - uses: pnpm/action-setup@v3
        with: { version: 9 }
      - uses: actions/setup-node@v4
        with: { node-version: 20, cache: pnpm }
      - run: pnpm install --frozen-lockfile
      - run: pnpm turbo lint typecheck test --filter=...[HEAD^1]
      - run: pnpm turbo build

Why Remote Cache Is Critical for CI?

Local cache works only on one machine. For teams and CI, remote cache is essential. According to Turborepo official documentation, remote caching can reduce CI build times by up to 80%. Vercel Remote Cache is free for open source, paid for private repos. A self-hosted option via turborepo-remote-cache:

# docker-compose.yml for remote cache server
services:
  turbo-cache:
    image: ducktors/turborepo-remote-cache:latest
    ports:
      - "3000:3000"
    environment:
      TURBO_TOKEN: "your-secret-token"
      STORAGE_PROVIDER: "s3"
      S3_BUCKET: "turbo-cache-bucket"
      AWS_ACCESS_KEY_ID: "${AWS_ACCESS_KEY_ID}"
      AWS_SECRET_ACCESS_KEY: "${AWS_SECRET_ACCESS_KEY}"

Table 1: Caching comparison: local vs remote

Table 2: Monorepo tool comparison

Common Mistakes and Solutions

• Not specifying env in pipeline — cache returns stale values.
• Forgetting persistent: true for dev — watcher doesn't start.
• Circular dependencies — check the dependency graph.
• Missing fetch-depth: 2 in CI — filter ...[HEAD^1] doesn't work.
• Incorrect remote cache setup — ensure TURBO_TOKEN and TURBO_TEAM are set.

Turnkey Turborepo Setup Process

We handle the full cycle: audit of current architecture, design of monorepo structure, configuration of turbo.json, creation of shared packages (TypeScript, ESLint, Tailwind), deployment of remote cache on S3, CI/CD integration, documentation, and team training. Result: builds 3–5 times faster, caching on CI, unified codebase. Development time savings can reach 80%.

What's Included in Our Service

• Detailed project audit and migration plan
• Set up Turborepo monorepo with all configurations
• Remote cache server deployment (Docker + S3)
• CI/CD pipeline integration (GitHub Actions, GitLab CI, etc.)
• Shared packages creation (TypeScript, ESLint, Tailwind presets)
• Comprehensive documentation and team onboarding
• 2 weeks of post-launch support and optimization

Timeline and Savings

Setting up from scratch for a project with 5–8 packages takes 2–3 days. Migrating an existing project to monorepo takes about a week. Cost is calculated individually, but our clients typically save $1,000–$3,000 per month on CI infrastructure. Over 50 monorepo projects completed, seven years in web development.

How Does Turborepo Speed Up Builds?

Task parallelization based on the dependency graph allows independent tasks to run simultaneously. Caching results (local and remote) skips rebuilding unchanged packages. The built-in --filter runs tasks only for affected packages and their dependencies. According to Turborepo official documentation, parallelization can reduce build time by up to 5x.

Conclusion

Turborepo is an efficient tool for accelerating CI and simplifying monorepo workflows. Proper configuration with remote cache and a well-designed pipeline yields noticeable time and resource savings. We offer turnkey monorepo setup in as little as 3 days. Contact us for a free project estimate — we'll help you identify potential savings and design an optimal solution.

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.