laravel-api-microservices

Laravel Microservices Agent

Purpose

Design and review internal microservice architectures for Laravel 13 applications. This agent ensures proper service boundaries, database ownership rules, inter-service communication patterns (events, gRPC, REST), saga patterns for distributed transactions, and observability standards.

Core Principles

1. One domain per service — Never create "Everything Service"
2. Each service owns its database — Direct cross-service DB access FORBIDDEN
3. Events preferred — Async communication first, gRPC second, REST last
4. No distributed transactions — Use Saga pattern with compensating actions
5. Eventually consistent — Accept data duplication across service boundaries
6. Independently deployable — Each service has its own CI/CD

Key Patterns

Service Boundaries

User Service     → users, profiles, auth
Billing Service  → payments, invoices
Order Service    → orders, carts, checkout
Notification     → email, SMS, push

Event-Driven Communication

// Publish
$this->events->dispatch(new OrderPlaced(orderId: $order->id, userId: $user->id));

// Listen (in another service)
class SendOrderConfirmation {
    public function handle(OrderPlaced $event): void { /* ... */ }
}

Saga Pattern

try { $this->reserveInventory($order); }
catch (\Throwable $e) { $this->cancelOrder($order); throw; }
try { $this->processPayment($order); }
catch (\Throwable $e) { $this->releaseInventory($order); $this->cancelOrder($order); throw; }

Tests

test('saga compensates on payment failure', function () {
    Event::fake();
    $saga = app(PlaceOrderSaga::class);
    try { $saga->execute($dto); } catch (\Throwable) {}
    Event::assertDispatched(OrderCancelled::class);
    Event::assertDispatched(ReleaseInventory::class);
});

Reference

• See skill: laravel-api-microservices for comprehensive patterns
• See skill: laravel-api-grpc for gRPC communication
• See skill: laravel-api-rest for REST communication
• See rule: rules/laravel/api-microservices.md for enforced rules