Event-driven architecture & CQRS Arquitectura orientada a eventos y CQRS
When every feature touches five services, you have a coupling problem — not a staffing problem. Explore RabbitMQ gateways, transaction services, and CQRS handlers used in reference architectures and production-minded write-ups. Cuando cada feature toca cinco servicios, el problema es acoplamiento — no headcount. Explora gateways RabbitMQ, servicios de transacciones y handlers CQRS usados en arquitecturas de referencia y artículos orientados a producción.
Related projects
Case studies with role, problem, impact, and stack breakdowns.
-
API Gateway (RabbitMQ)
NestJS API Gateway routing HTTP requests to microservices via RabbitMQ.
-
Microservices Architecture
NestJS microservices with RabbitMQ for user and transaction management.
-
Users Microservice (RabbitMQ)
Dedicated users microservice with RabbitMQ for distributed user management and auth events.
-
Banking Platform (Microservices + Events)
Three NestJS microservices with PostgreSQL per service and a Kafka-compatible event bus (Redpanda).
Related articles
Summaries on andresed.dev with links to full posts on Making Code.
-
Your API Doesn't Need More Services, It Needs Events
If every new feature forces you to modify five different services, you probably have a coupling problem. Event-Driven Architecture to decouple NestJS modules.
-
CQRS in NestJS: Stop Mixing Reads and Writes in the Same Service
When your UserService handles POST and GET, optimizations on one side break the other. Commands, queries, and handlers with @nestjs/cqrs.