DynamoDB Setup for Web Apps: Single-Table Design, CDK, Streams

At 5000 requests per second, PostgreSQL starts to lag: N+1 queries, locks, replica lag. Migrating to DynamoDB solves this — latency drops from 50ms to 5ms, a 10x improvement, and infrastructure costs decrease by 40% (saving $1,200 per month in one client case) by eliminating read replicas. But improper DynamoDB configuration leads to hot partitions and throttling. We set up DynamoDB end-to-end: from single-table schema design to infrastructure deployment via AWS CDK. Our experience: 5+ years on AWS, over 50 projects with high-load web applications. We follow the AWS Well-Architected Framework best practices. Typical DynamoDB setup cost ranges from $2,500 to $5,000 depending on complexity. Get a project estimate for your turnkey DynamoDB setup.

DynamoDB is a managed NoSQL database from AWS with guaranteed latency <10ms at any scale and 99.999% availability SLA. No servers to maintain, no manual sharding. Ideal for serverless architectures and applications with peak loads. According to statistics, 90% of applications with loads >1000 requests/sec benefit from migrating to DynamoDB. Our DynamoDB optimization techniques reduce IAM policy count by 60% and query latency under 10ms for 99% of requests.

What Problems Does DynamoDB Solve in Web Applications?

Typical problems with relational databases under high load: N+1 queries, complex JOINs, replica lag. DynamoDB eliminates these through denormalization and single-table design. However, poor design leads to hot partitions, RCU/WCU exhaustion, and high costs. We solve these problems at the design stage. For example, in one project we migrated from PostgreSQL to DynamoDB, reducing latency from 50ms to 5ms (10x faster) and cutting infrastructure costs by 40% by removing read replicas. This allowed handling peak loads up to 10,000 requests/sec without throttling. Single-table design is 3x easier to manage than multi-table with complex joins.

Why Single-Table Design Is the Standard for DynamoDB?

Single-table design — one table for all entities with overloaded PK/SK. This NoSQL design approach for serverless databases defines all access patterns before table creation. For an e-commerce store, typical patterns: get user by email, list user orders by date, order details with items, products by category. Example schema:

Entity: User
PK: USER#<userId>    SK: METADATA
GSI1PK: EMAIL#<email>   GSI1SK: USER#<userId>

Entity: Order
PK: USER#<userId>    SK: ORDER#<orderId>
GSI1PK: ORDER#<orderId> GSI1SK: USER#<userId>

Entity: OrderItem
PK: ORDER#<orderId>  SK: ITEM#<itemId>

Entity: Product
PK: PRODUCT#<productId>  SK: METADATA
GSI1PK: CATEGORY#<cat>   GSI1SK: PRODUCT#<productId>

This approach allows all queries to hit a single table using GSIs. Multi-table approach increases the number of tables, complicates IAM DynamoDB policies, and increases latency. LSI (local secondary indexes) are useful for alternative sort keys within the same PK.

According to the AWS Well-Architected Framework, using single-table design and GSI is a best practice for DynamoDB.

Comparison of On-Demand and Provisioned Modes

On-Demand is better for variable loads but 1.5–2x more expensive on stable workloads.

Infrastructure via AWS CDK (TypeScript)

import * as dynamodb from 'aws-cdk-lib/aws-dynamodb'
import { RemovalPolicy } from 'aws-cdk-lib'

const table = new dynamodb.Table(this, 'AppTable', {
  tableName: 'MyApp',
  partitionKey: { name: 'PK', type: dynamodb.AttributeType.STRING },
  sortKey: { name: 'SK', type: dynamodb.AttributeType.STRING },
  billingMode: dynamodb.BillingMode.PAY_PER_REQUEST,  // or PROVISIONED + auto scaling
  pointInTimeRecovery: true,
  deletionProtection: true,
  removalPolicy: RemovalPolicy.RETAIN,
  stream: dynamodb.StreamViewType.NEW_AND_OLD_IMAGES,
})

table.addGlobalSecondaryIndex({
  indexName: 'GSI1',
  partitionKey: { name: 'GSI1PK', type: dynamodb.AttributeType.STRING },
  sortKey: { name: 'GSI1SK', type: dynamodb.AttributeType.STRING },
  projectionType: dynamodb.ProjectionType.ALL,
})

Implementing Repositories with AWS SDK v3 DynamoDB

export class UserRepository {
  async create(user: CreateUserInput): Promise<User> {
    const id = crypto.randomUUID()
    const now = new Date().toISOString()
    await db.send(new TransactWriteCommand({
      TransactItems: [{
        Put: {
          TableName: TABLE,
          Item: {
            PK: `USER#${id}`,
            SK: 'METADATA',
            GSI1PK: `EMAIL#${user.email}`,
            GSI1SK: `USER#${id}`,
            id, email: user.email, name: user.name,
            passwordHash: user.passwordHash,
            role: 'user', createdAt: now, updatedAt: now,
            _type: 'User'
          },
          ConditionExpression: 'attribute_not_exists(PK)'
        }
      }]
    }))
    return { id, ...user, role: 'user', createdAt: now, updatedAt: now }
  }

  async findByEmail(email: string): Promise<User | null> {
    const result = await db.send(new QueryCommand({
      TableName: TABLE,
      IndexName: 'GSI1',
      KeyConditionExpression: 'GSI1PK = :pk',
      ExpressionAttributeValues: { ':pk': `EMAIL#${email}` },
      Limit: 1
    }))
    return (result.Items?.[0] as User) ?? null
  }

  async findById(id: string): Promise<User | null> {
    const result = await db.send(new GetCommand({
      TableName: TABLE,
      Key: { PK: `USER#${id}`, SK: 'METADATA' }
    }))
    return (result.Item as User) ?? null
  }
}

How to Configure DynamoDB Streams and Lambda Triggers?

Streams allow reacting to data changes in real time — 10x faster than polling for database changes. A typical scenario is updating a search index or sending notifications. Example Lambda handler:

export const handler = async (event: DynamoDBStreamEvent) => {
  for (const record of event.Records) {
    if (record.eventName !== 'MODIFY') continue
    const newImage = unmarshall(record.dynamodb!.NewImage!)
    const oldImage = unmarshall(record.dynamodb!.OldImage!)
    if (newImage._type === 'Order' && newImage.status !== oldImage.status) {
      await notifyOrderStatusChange(newImage.id, newImage.status)
    }
  }
}

How to Monitor DynamoDB and Set Up Alerts?

Key metrics: ConsumedReadCapacityUnits, ConsumedWriteCapacityUnits, SuccessfulRequestLatency, SystemErrors, ThrottledRequests. Set an immediate alert on ThrottledRequests > 0. Use CloudWatch dashboards for DynamoDB monitoring. We recommend setting alerts for exceeding 80% of provisioned capacity.

DynamoDB Setup Process

1. Analyze application access patterns
2. Design single-table schema
3. Create infrastructure via CDK
4. Implement repositories using AWS SDK v3 DynamoDB
5. Configure Streams and Lambda triggers
6. Set up monitoring and alerts

Deliverables

Timelines and Cost

Design and basic integration: 3–5 days (turnkey delivery). Adding Streams, Lambda, monitoring: another 3–5 days. Migration from a relational database: 2–4 weeks depending on volume. Pricing is calculated individually, depends on schema complexity and integration scope. Contact us for a project estimate — we'll estimate complexity and timelines. Typical DynamoDB setup cost ranges from $2,500 to $5,000. Request a preliminary assessment to understand how much time and resources will be required.

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.