Event Sourcing: Practical Implementation Guide with Code

Imagine an e-commerce site processing 10,000 orders per day. A customer cancels an order, a manager changes the status, and the system loses the history. Restoring the action chain is impossible—the database only holds the current state. Without Event Sourcing, auditing requires workarounds: logging, triggers, extra tables. One of our fintech clients spent two months investigating an incident because no history existed. After implementing this pattern, we cut audit time by 80%, saving the client over $50,000 per year. For a typical mid-size project, our Event Sourcing implementation reduces audit costs by 80%, saving $40,000 annually. Our team has 5+ years of proven Event Sourcing expertise and has completed more than 10 projects, guaranteeing reliable implementations.

Event Sourcing is a key pattern in event-driven architecture where every state change is captured as an immutable event. The current state is rebuilt by replaying all events. Event Sourcing is a design pattern that stores a sequence of events.

Event Sourcing Architecture: Event Store, Aggregates, and Replay

Event Store — The Foundation

The main table is append-only. No UPDATE or DELETE allowed:

CREATE TABLE event_store (
  id           BIGSERIAL PRIMARY KEY,
  event_id     UUID UNIQUE NOT NULL,
  aggregate_id UUID NOT NULL,
  aggregate_type VARCHAR(100) NOT NULL,
  event_type   VARCHAR(100) NOT NULL,
  event_version INT NOT NULL DEFAULT 1,
  payload      JSONB NOT NULL,
  metadata     JSONB NOT NULL DEFAULT '{}',
  occurred_at  TIMESTAMPTZ NOT NULL DEFAULT NOW(),
  sequence_nr  BIGINT NOT NULL  -- global order
);

CREATE INDEX idx_es_aggregate ON event_store (aggregate_id, aggregate_type, id);
CREATE INDEX idx_es_sequence ON event_store (sequence_nr);

Optimistic locking — checking sequence_nr before writing a new event prevents concurrent write conflicts. We use a PostgreSQL Event Store for reliable and cost-effective storage, which is 10x cheaper than specialized solutions while providing adequate performance for 95% of projects.

Aggregates: Business Logic on Events

An event aggregate encapsulates business rules and state. It applies events to transition state.

class OrderAggregate {
  private state: OrderState = { status: 'new', items: [], total: 0 };
  private version = 0;
  private uncommittedEvents: DomainEvent[] = [];

  static rehydrate(events: DomainEvent[]): OrderAggregate {
    const order = new OrderAggregate();
    for (const event of events) {
      order.apply(event);
    }
    return order;
  }

  placeOrder(items: OrderItem[]) {
    if (this.state.status !== 'new') throw new Error('Order already placed');

    this.raise({
      eventType: 'OrderPlaced',
      payload: { items, placedAt: new Date() }
    });
  }

  private apply(event: DomainEvent) {
    switch (event.eventType) {
      case 'OrderPlaced':
        this.state.status = 'placed';
        this.state.items = event.payload.items;
        break;
      case 'PaymentProcessed':
        this.state.status = 'paid';
        this.state.paidAmount = event.payload.amount;
        break;
      case 'OrderShipped':
        this.state.status = 'shipped';
        this.state.trackingNumber = event.payload.trackingNumber;
        break;
    }
    this.version++;
  }
}

Replay and Snapshots

When an aggregate has many events (over 500), full replay becomes slow. A snapshot is a serialized state at event N. On load, we read the latest snapshot plus events after it.

Snapshots Improve Performance

async loadAggregate(aggregateId: string): Promise<OrderAggregate> {
  const snapshot = await this.snapshotRepo.findLatest(aggregateId);
  const fromSequence = snapshot?.version ?? 0;

  const events = await this.eventStore.getEvents(
    aggregateId, { fromVersion: fromSequence }
  );

  const aggregate = snapshot
    ? OrderAggregate.fromSnapshot(snapshot)
    : new OrderAggregate();

  return aggregate.rehydrate(events);
}

State restoration is achieved by replaying events from the event store. Snapshots are created asynchronously every 100–500 events per aggregate. Optimistic locking during event write checks sequence_nr — if changed, the write is rejected, ensuring integrity.

Time complexity of operations:

How to handle projections and schema evolution

Projections (Read Models) for Fast Reads

This pattern mandates separating Write Model (events) from Read Model (projections for queries). This is a typical CQRS implementation. Event projections subscribe to the event stream and build denormalized tables:

class OrderProjection {
  async on(event: DomainEvent) {
    switch (event.eventType) {
      case 'OrderPlaced':
        await db.query(`
          INSERT INTO orders_view (id, status, customer_id, total, created_at)
          VALUES ($1, 'placed', $2, $3, $4)
        `, [event.aggregateId, event.payload.customerId,
            event.payload.total, event.occurredAt]);
        break;

      case 'OrderShipped':
        await db.query(`
          UPDATE orders_view SET status = 'shipped',
            tracking_number = $2, shipped_at = $3
          WHERE id = $1
        `, [event.aggregateId, event.payload.trackingNumber, event.occurredAt]);
        break;
    }
  }
}

Projections can be dropped and rebuilt from scratch — the event history is complete.

Schema Evolution: Avoiding History Breaks

Versioning event schemas is mandatory. Strategies:

• Upcasting — transform old events to new schema on read.
• Weak schema — JSON allows adding fields without breakage.
• Event versioning — store eventVersion, read with different handlers.

Tools for Event Store

Ready solutions:

• EventStoreDB — specialized DB with subscriptions and projections.
• Marten (.NET) — PostgreSQL as Event Store + document DB.
• Axon Framework (Java) — full ES/CQRS framework.

A custom PostgreSQL Event Store is sufficient for most projects. Use LISTEN/NOTIFY to notify projections of new events. Use a message broker (Kafka, RabbitMQ, NATS JetStream) for distribution across services.

Comparison of Event Store implementations:

Implementation Plan and Timeline

1. Domain analysis and aggregate identification (1–2 weeks).
2. Define event types and schemas (3–5 days).
3. Implement Event Store (PostgreSQL or ready solution) — 2–3 days.
4. Write aggregates with business logic (3–5 days per aggregate).
5. Build projections for read models (5–7 days).
6. Set up snapshots for performance (1–2 days).
7. Integrate with message broker (Kafka, RabbitMQ) — 3–5 days.
8. Testing and monitoring (1–2 weeks).

Timeline: Base Event Store on PostgreSQL — 2–3 days. One aggregate — 3–5 days. Projections + subscriptions + snapshots — another 5–7 days. Full system with multiple aggregates, schema evolution, and monitoring — 3–5 weeks.

What Is Included in the Work

Deliverables

• Documentation on events and schemas.
• Code for aggregates, projections, and snapshots.
• Event Store setup (PostgreSQL or EventStoreDB).
• Integration with a message broker.
• Access to the event store and monitoring dashboards.
• Team training on Event Sourcing.
• Post-implementation support (1 month).

Benefits of Event Sourcing

• Complete audit trail for every change.
• Ability to roll back to any state.
• Separation of write and read models (CQRS).
• Easy addition of new projections without migrations.

The event-driven architecture with PostgreSQL Event Store uses event aggregates, event projections, CQRS, snapshots, event schema versioning, and state restoration for complete audit trail.

Get a consultation — we will analyze your domain and propose the optimal solution. Contact us to assess your project. We will help implement Event Sourcing tailored to your requirements.

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.