The foundations for designing each Laravel module as a microservice: its code runs in a context bounded to its module, blind to the others, whether they run here or elsewhere, and it talks to them only through contracts and events. Whether modules run as microservices or several to a process, depending on load, release pace or cost, becomes an infrastructure choice rather than a code one, allowing greater flexibility.

Laravel apps as microservices: signed RPC through contracts, ordered events with an outbox, and read-only copies of another service's rows.

Outbox Stack mail driver and webhooks for Laravel

Correctness infrastructure for durable execution, ambiguity detection, safe recovery, and reconciliation of irreversible remote operations in Laravel.

Durable integration operation kernel for Laravel applications and provider SDKs

Durable, tenant-aware AI workflow compilation and execution for Laravel

The SIEM log-streaming delivery engine for Laravel — a durable transactional outbox, queued batched delivery with retry/backoff/dead-letter/circuit-breaker, SSRF-guarded egress to HTTP collectors, Datadog, Amazon S3 and Google Cloud Storage, encrypted destination secrets, and PII redaction, on top of the framework-agnostic cboxdk/siem core.

Reliable Laravel service-to-service messaging with signed outbox/inbox envelopes, idempotency, retries, callbacks, observability, and security audit tooling.

Transactional outbox for Laravel: stage messages inside your database transaction and relay them reliably with retries and backoff.

Laravel package for Transactional Outbox/Inbox patterns

Transactional outbox for Laravel: events and jobs persisted atomically with your business writes, then replayed reliably with backoff and dead-letter handling.