Question 1

What is Ecotone?

Accepted Answer

Ecotone is the PHP architecture layer for durable workflows, event sourcing, Domain-Driven Design, reliable messaging, and asynchronous communication — one Composer package that adds sagas, orchestrators, aggregates, projections, outbox, retries, and CQRS to Laravel, Symfony, or Tempest through declarative PHP attributes. It runs on the database and broker you already operate; no separate workflow service, no replay-deterministic DSL, no engine-specific event log.

Question 2

Do I need Temporal or a separate workflow engine to build durable workflows in PHP?

Accepted Answer

No. Ecotone delivers durable execution on the database and broker you already run. Sagas persist state per identifier, chained workflows survive crashes through the outbox plus async channel, saga timeouts use a #[Delayed] attribute, and Orchestrators (Enterprise) give declarative multi-step workflows. There is no separate cluster to operate, no RoadRunner or ext-grpc requirement, no replay-deterministic DSL — workflows are plain PHP classes with attributes. If you have already adopted Temporal, Ecotone still fits around it for CQRS, projections, distributed messaging, multi-tenant routing, and sagas that aren't full workflows.

Question 3

Which message brokers does Ecotone work with?

Accepted Answer

RabbitMQ, Apache Kafka, Amazon SQS, Redis, and the database (DBAL outbox) are first-party — and Ecotone also integrates with Enqueue transports, Symfony Messenger transports, and Laravel Queue channels. Handler code is broker-agnostic: a single #[Asynchronous('channel')] attribute works the same across every transport. CombinedMessageChannel writes the message to the database for the outbox guarantee and dispatches execution on the broker, so outbox draining stays on the database and consumers scale horizontally on RabbitMQ / SQS / Kafka.

Question 4

Can I use Ecotone with Laravel, Symfony, or Tempest?

Accepted Answer

Yes. Ecotone ships dedicated packages for Laravel, Symfony, and Tempest that make integration seamless. After installation, Command, Event, and Query buses are available out of the box in the dependency container — and for any other framework, Ecotone Lite provides a standalone integration via PSR-11.

Question 5

Do I need to rewrite my application to use Ecotone?

Accepted Answer

No. Ecotone works alongside your existing application — you adopt it incrementally for the parts where messaging, sagas, event sourcing, or distributed messaging make sense, without rewriting what already works. Ecotone sits above Symfony Messenger and Laravel Queues, using them as transports underneath rather than replacing them.

Question 6

Why pick Ecotone for Event Sourcing?

Accepted Answer

Ecotone provides a built-in event store on PostgreSQL or MySQL with #[EventSourcingAggregate], #[ProjectionV2] for read models (global, partitioned, or streaming), non-blocking gap detection that catches concurrent-transaction events without blocking concurrent writes, projections that can publish their own events so dependents react in the same flow instead of a separate eventually-consistent process (with rebuild auto-suppression), and end-to-end PII encryption across the event store, broker payloads, and structured logs. As event volume grows, projections scale from a single cursor to N parallel workers via partitioning — without changing your domain code.

Question 7

Does Ecotone support building systems following Domain-Driven Design?

Accepted Answer

Ecotone's vocabulary is DDD vocabulary: #[Aggregate], Repository abstraction, #[Saga] as process managers, bounded-context isolation via the Distributed Bus, and Domain Events as first-class plain PHP classes. Where each building block is fully decoupled from the framework using declarative configuration. Ecotone is the only architecture layer that makes DDD building blocks easily composable in Message-Driven systems, to not only ensure clear business logic, but to make the system build on top of reliable architecture.

Features	Free	Enterprise
CQRS and Message Bus
Asynchronous Messaging
Managing Handlers execution (Delay, Expiration, Priority)
Metadata Support
Aggregates
Workflow Support
Sagas
Event Sourcing
Event Projecting
Partitioned Projections
Async Backfill & Rebuild
Blue-Green Projection Deployments
Streaming Projections
Interceptors Support
Retries (Instant, Delayed, Exponential)
Error Channel and Dead Letter
Outbox Support
Idempotency Support
AMQP Distributed Bus
Testing Support
Tracing and OpenTelemetry Support
Multi-Tenancy (Connection Routing)	Free in 1.x
Dynamic Message Channels
Advanced Event Sourcing Handlers
Kafka Integration
Asynchronous Message Buses
Non-blocking, Batched Delivery
Distributed Bus with Service Map
Rabbit Consumer
RabbitMQ Streaming Channel
Command Bus Instant Retries
Command Bus Error Channel
Gateway-Level Deduplication
Instant Aggregate Fetch
Orchestrators
Async Endpoint Annotations
Durable Execution Without a Separate Service
Closures as Expressions (PHP 8.5)

Choose your plan

Free

Enterprise

Enterprise Plus

Want to evaluate Enterprise first?

Compare plans & features

Need a formal Support Agreement?

Frequently asked questions

Need help?

Email us

Join our community

Read docs on Enterprise features