Why Ecotone?

Why Ecotone — the PHP architecture layer that grows with your system, without rewrites

What Ecotone Is (and Isn't)

Ecotone is not a framework replacement. You don't rewrite your Laravel or Symfony application to use Ecotone — you add it.

Ecotone is a Composer package that adds architecture on top of your framework: command, query, and event buses wired from attributes; aggregates as plain PHP classes; sagas and projections as first-class patterns; event sourcing, transactional outbox, and distributed messaging all on the same messaging foundation.

You keep your ORM (Eloquent or Doctrine), your routing, your templates, your deployment. Ecotone provides the architecture layer — the part that keeps your system maintainable as complexity grows.

# Your framework stays. Ecotone adds the architecture on top.
composer require ecotone/laravel
# or
composer require ecotone/symfony-bundle

One Package That Grows With Your System

The core promise of Ecotone: no forced architectural migrations as your domain grows. Every other PHP choice commits to a ceiling on day one. Spatie laravel-event-sourcing has no sagas. EventSauce assembles everything around it. Patchlevel has no outbox or distributed bus. Symfony Messenger is dispatch-only; aggregates, ES, sagas, and outbox are all separate library decisions.

With Ecotone, you start with #[CommandHandler] on day one. You add #[Asynchronous] when you need async. You add #[Saga] when you need a stateful workflow. You add #[EventSourcingAggregate] when audit and replay become requirements. You add #[DistributedBus] when your system splits into services.

The same codebase, the same classes, new attributes next to the old ones. No library swap. No parallel stack. No "migration from library A to library B" week.

Patterns Proven in Other Ecosystems — Now on PHP

Ecotone is built on Enterprise Integration Patterns, the same foundation behind:

Ecosystem	Pattern-driven architecture layer
Java	Spring Integration, Axon Framework
.NET	NServiceBus, MassTransit, Wolverine
PHP	Ecotone

The patterns are decades-tested in banking, telecom, and logistics systems. Ecotone brings them to PHP as attribute-driven code on your existing Laravel or Symfony application — so your team writes POPOs, and Ecotone applies the patterns.

What You Get, Mapped to Problems

Instead of learning pattern names first, start with the problem you're solving:

Your problem	What the industry calls it	Ecotone feature
Business logic is scattered across controllers and services	CQRS (Command Query Responsibility Segregation)	Message Bus and CQRS
You need a full audit trail and the ability to rebuild state	Event Sourcing	Event Sourcing
Complex multi-step processes are hard to follow and maintain	Sagas, Workflow Orchestration	Business Workflows
Async processing is unreliable and hard to debug	Resilient Messaging	Resiliency
Retried handlers re-run sibling handlers and produce duplicate side effects	Per-handler failure isolation	Resiliency
Complex routing flows collapse into conditional dispatch code	EIP composable messaging (pipes, content-based routing, splitters)	Business Workflows
Renaming a command class breaks in-flight messages	Endpoint-ID routing	Message Bus and CQRS
Services need to communicate reliably across boundaries	Distributed Messaging	Distributed Bus
Webhooks arrive twice and double-charge customers	Deduplication, per-bus retry/DLQ policy	Resiliency
Multiple tenants need isolated processing with their own queues and priorities	Multi-Tenant messaging	Multi-Tenancy Support

How It Integrates

Ecotone plugs into your existing framework without requiring changes to your application structure.

Laravel

Laravel's queue runs jobs, not business processes — anything resembling aggregates, sagas, workflows, or event sourcing ends up stitched together from separate libraries. Ecotone fills that layer directly: works with Eloquent for aggregate persistence, Laravel Queues for async message channels, and Laravel Octane for high-performance scenarios. Configuration via your standard Laravel config files.

composer require ecotone/laravel

Laravel Module Documentation

Symfony

Symfony Messenger handles dispatch — aggregates, sagas, event sourcing, and transactional outbox are left to you. Ecotone fills that layer directly: works with Doctrine ORM for aggregate persistence, Symfony Messenger Transport for async message channels, and standard Bundle configuration. Ecotone auto-discovers your attributes in the src directory.

composer require ecotone/symfony-bundle

Symfony Module Documentation

Standalone

For applications without Laravel or Symfony, Ecotone Lite provides the full feature set with minimal dependencies.

composer require ecotone/lite-application

Ecotone Lite Documentation

Trusted in Regulated Production

Ecotone runs in production at payment gateways where retried handlers cannot double-charge, at credit card systems where transaction loss is catastrophic, at certification authorities whose event log is the audit log, at e-commerce platforms orchestrating order-payment-fulfillment sagas, at public transportation subscription systems managing nationwide transit subscriptions with Kafka integration to Java services, and at two-sided marketplaces coordinating customer orders, provider subscriptions, and B2B partnerships.

The capabilities on Ecotone's feature set are not hypothetical. They run in systems where failure is either regulated, expensive, or public.

Start Today, Grow Into Every Pattern

Day one: install the package, add #[CommandHandler] to one method, run your tests.

Week one: add #[Asynchronous] to move handlers off the request cycle.

Month three: add #[Saga] for your first multi-step business process; add the transactional outbox.

Year two: event-source the aggregates where audit matters; add distributed bus when your system splits into services.

Same classes. Same codebase. Same team. No forced migration between stages.

Learn about Enterprise features for advanced multi-tenancy, distributed bus with service map, orchestrators, and production-grade Kafka.