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.

Starter kit for laravel-distributable-modules: a modular monolith deployable as one process or as per-module services.

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

HTTP driver for the RPC of mk-josias/laravel-microservices: signed calls between services, one endpoint per service.

Laravel queue driver for the events of mk-josias/laravel-microservices, for a stack without Redis: one queue per service; order is not kept after a failure.

Redis Streams driver for the events of mk-josias/laravel-microservices: one ordered stream, a consumer group per service, failed entries retried before later ones.