/ A. Pozo

Selected work

Proof, not promises.

Two live engagements, anonymised. Each is the same thesis under real production load: domain-driven architecture that gets cheaper to extend, not more expensive. Outcomes verifiable on request.

Two engagements. Two stacks. One architecture, proven twice.

0
Live engagements
0
Architectural kernels built
0
Bounded contexts modelled
0
Legacy lines retired

The common kernel

Both engagements run on the same hand-built kernel.

Commands change state, queries read it, and domain events let the rest of the system react — over a CQRS message bus. Around the domain, ports and adapters keep it pure. The same kernel is reused by every bounded context in both case studies.

CQRS message bus live
CommandBus Command Write model QueryBus Query Read model EventBus Event Subscribers
Ports & adapters live
HTTP Scheduler PostgreSQL Message queue Domain pure · no framework driving driven

Case studies

Each project is the same idea, tested differently.

01 Enterprise · B2B SaaS 2025

A domain-driven kernel for Spring Boot — and the bounded context that proved it

A Spring Boot 4 / Java 25 backend refactored from a layered monolith into an explicit domain-driven architecture. Two deliverables: an in-house architectural kernel — CQRS buses, saga engine, transactional outbox, idempotence, declarative criteria, value-object primitives — and a first bounded context built on it as proof, replacing a 743-line legacy service with fifteen single-responsibility application services and a transactional saga.

  • Backend Architecture
  • DDD
  • CQRS
  • Hexagonal
Backend Architect · Kernel & Migration Lead Read case study →
02 B2B Operations · HR & Payroll 2025

An HR attendance and cash-flow platform, modelled as bounded contexts in NestJS

A full-stack monorepo (NestJS + React 19 + Prisma) for HR operations: schedules, payroll closures, deductions, charges, payments and cash-flow accounts. Same domain-driven discipline as a sibling Java/Spring backend — Hexagonal, DDD, CQRS — deliberately ported to TypeScript with a kernel of 83 in-house primitives.

  • Backend Architecture
  • DDD
  • CQRS
  • Hexagonal
Full-Stack Architect · Backend Lead Read case study →

Working together

Your system could be the next proof.

If you're rebuilding a critical part of your operation and want architecture that compounds instead of decaying, I'd like to hear about it.

Start a conversation How I work