Complete Guide to SQLAlchemy Configuration for Python Web Applications

Typical Problem with Sessions

FastAPI developers often encounter a situation: the app works locally, but in production after 10 minutes — an SSL SYSCALL error or BrokenPipeError. The cause is that the connection pool contains dead sockets. SQLAlchemy 2.0 with the pool_pre_ping option solves this, but proper configuration is only part of the path. Without correct setup of async sessions and migrations, you risk N+1 queries and MissingGreenlet errors under load.

We have been configuring SQLAlchemy for Python web applications on FastAPI and Flask for over five years, completing over 50 projects. During this time we've collected a set of best practices that guarantee stability even at 1500+ requests per second. In this article we'll break down key components: from async session to automatic Alembic migrations. The SQLAlchemy 2.0 Documentation recommends exactly this approach.

For example, in one project with a peak load of 2000 RPS we encountered TimeoutError due to the lack of pool_pre_ping. After implementing this option and increasing the pool to 30 connections, response time dropped by 40%. Such results are only possible with correct configuration of the entire chain.

How to Configure an Async Session for FastAPI (Step-by-Step)

1. Install asyncpg and SQLAlchemy: pip install asyncpg sqlalchemy[asyncio].
2. Create engine with create_async_engine:

from sqlalchemy.ext.asyncio import AsyncSession, async_sessionmaker, create_async_engine
from sqlalchemy.orm import DeclarativeBase

DATABASE_URL = "postgresql+asyncpg://user:pass@localhost:5432/mydb"

engine = create_async_engine(DATABASE_URL, pool_size=10, max_overflow=20, pool_pre_ping=True, echo=False)
AsyncSessionLocal = async_sessionmaker(engine, class_=AsyncSession, expire_on_commit=False)

class Base(DeclarativeBase):
    pass

pool_pre_ping=True checks the connection before using it — mandatory for production. Without it, dead connections cause 500 errors, especially in cloud environments with long timeouts. Additionally, set pool_recycle to 3600 seconds for automatic replacement of old connections.

3. Inject the session via dependency injection: create a get_db dependency that opens a session, performs commit or rollback.

Why expire_on_commit=False is Critical for Async

By default after commit() SQLAlchemy expires all objects. Accessing attributes in async mode causes MissingGreenlet. Disabling it keeps objects available without extra queries. This boosts performance by about 20% and eliminates many debug sessions.

Models and Queries in 2.0 Style

The new typed API: Mapped + mapped_column instead of the old Column. Example of a user model with a relationship:

from datetime import datetime
from typing import Optional
from sqlalchemy import String, Enum, func
from sqlalchemy.orm import Mapped, mapped_column, relationship
from app.database import Base
import enum

class UserRole(enum.Enum):
    admin = "admin"
    editor = "editor"
    viewer = "viewer"

class User(Base):
    __tablename__ = "users"

    id: Mapped[int] = mapped_column(primary_key=True, autoincrement=True)
    email: Mapped[str] = mapped_column(String(320), unique=True, nullable=False)
    password_hash: Mapped[str] = mapped_column(String(255), nullable=False)
    role: Mapped[UserRole] = mapped_column(Enum(UserRole), default=UserRole.viewer, nullable=False)
    created_at: Mapped[datetime] = mapped_column(server_default=func.now(), nullable=False)
    updated_at: Mapped[datetime] = mapped_column(server_default=func.now(), onupdate=func.now(), nullable=False)

    posts: Mapped[list["Post"]] = relationship(back_populates="author", lazy="selectin")

lazy="selectin" — a safe strategy for async: executes a separate SELECT ... WHERE id IN (...), no MissingGreenlet. Compared to joinedload, it avoids giant JOINs, giving a performance boost up to 30% on queries with many relationships.

Queries:

from sqlalchemy import select
from app.models.user import User
from app.models.post import Post

async def get_published_posts_with_authors(db: AsyncSession, limit: int = 20, offset: int = 0) -> list[Post]:
    stmt = select(Post).join(Post.author).where(Post.status == "published").order_by(Post.created_at.desc()).limit(limit).offset(offset)
    result = await db.execute(stmt)
    return list(result.scalars().all())

Transactions and Migrations

For isolation of operations use nested transactions: async with db.begin_nested():. This is convenient for rolling back individual operations without reverting the entire transaction.

Configuring Alembic for async:

Initialization:

alembic init -t async alembic

Edit alembic/env.py:

from logging.config import fileConfig
from sqlalchemy.ext.asyncio import async_engine_from_config
from alembic import context
from app.database import Base
import app.models  # noqa: F401

config = context.config
fileConfig(config.config_file_name)
target_metadata = Base.metadata

def run_migrations_online():
    connectable = async_engine_from_config(config.get_section(config.config_ini_section), prefix="sqlalchemy.")
    async def do_run():
        async with connectable.connect() as connection:
            await connection.run_sync(context.configure, connection=connection, target_metadata=target_metadata, compare_type=True)
            async with context.begin_transaction():
                await connection.run_sync(context.run_migrations)
    import asyncio
    asyncio.run(do_run())
run_migrations_online()

compare_type=True — Alembic will track type changes. This saves time during refactoring.

Common Errors from Incorrect Configuration

Comparison of Sync and Async Approaches

Async approach gives a 3x increase in requests per second, which is critical for high-load projects. This makes async 3 times better than sync for high-traffic applications.

What's Included in the Work

• Audit of current SQLAlchemy configuration and identification of bottlenecks.
• Setup of async session with pool_pre_ping, optimization of connection pool.
• Design of models with correct lazy strategies and typing.
• Implementation of Alembic migrations with autogeneration and type control.
• Integration of session into FastAPI/Flask via dependency injection.
• Operations documentation and deployment instructions.
• Post-deployment support: 2 weeks of consultations.

Timelines and Cost

We provide a turnkey solution: setting up SQLAlchemy from scratch for a new project takes from 1 business day, costing from $500. Migrating an existing application from 1.4 to 2.0 — from 2 days, priced from $1,200. Cost is calculated individually after assessing the volume of models and queries.

Get a consultation for your project — our specialists will help configure SQLAlchemy to avoid problems under load. Order an audit of your current configuration and receive specific recommendations for performance improvement. We guarantee production reliability with 5+ years of experience and over 50 successful projects.

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.