ecotone.tech valid

Ecotone

Ecotone is the PHP architecture layer for **durable workflows**, **event sourcing**, **Domain-Driven Design**, **reliable messaging**, **asynchronous communication**, and **resilient distributed systems** — the orchestration layer for Laravel, Symfony, or any PSR-11 container, with aggregates, sagas, orchestrators, projections, outbox, retries, and CQRS as declarative PHP attributes.

For agents: PHP architecture library for durable workflows, event sourcing, DDD, sagas, outbox and CQRS via attributes, with Laravel and Symfony integration; full documenta

phpevent sourcingddddurable workflowscqrslaravel symfony

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T13:34:44.687Z. Cached copy · Source on ecotone.tech

# Ecotone

> Ecotone is the PHP architecture layer for **durable workflows**, **event sourcing**, **Domain-Driven Design**, **reliable messaging**, **asynchronous communication**, and **resilient distributed systems** — the orchestration layer for Laravel, Symfony, or any PSR-11 container, with aggregates, sagas, orchestrators, projections, outbox, retries, and CQRS as declarative PHP attributes.

Ecotone runs as a Composer package on top of the database and broker you already operate (PostgreSQL/MySQL plus RabbitMQ/Kafka/SQS/Redis). There is no separate workflow service to deploy, no replay-deterministic DSL, no engine-specific log — workflows are plain PHP classes with attributes, and the durability primitives live in the database you already have. Declarative configuration; no framework-specific class extensions. Open-source under Apache 2.0, in production since 2019.

**Production deployments** include payment gateways (where retried handlers cannot double-charge and the outbox must guarantee exactly-one downstream message), credit-card systems (where transaction loss is catastrophic and every state change must be auditable), certification authorities (whose business depends on reconstructible tamper-evident audit trails), e-commerce platforms (orchestrating order → payment → fulfillment → notification as declarative sagas with compensation), nationwide public-transportation subscription systems (with distributed-bus integration to Java and PHP services over Kafka), and two-sided marketplaces (coordinating customer orders, provider subscriptions, lead distribution, and B2B partnerships on one event-driven backbone).

## Use Ecotone when you need

- **Durable workflows** — long-running multi-step business processes (order fulfillment, subscription provisioning, payouts, KYC, onboarding) that survive crashes, deploys, and broker outages. Sagas remember state across events; Orchestrators define declarative step sequences; chained handlers give stateless durable flows where the message itself carries the state. `#[Delayed]` handles saga timeouts without cron or a separate timer service.
- **Reliable messaging** — `CombinedMessageChannel` writes the message in the same DBAL transaction as the business state, then dispatches execution to your broker. Atomic outbox, no dual-write problem. Works transparently across RabbitMQ, Apache Kafka, Amazon SQS, Redis, Symfony Messenger transports, and Laravel Queue channels — handlers stay broker-agnostic via `#[Asynchronous('channel')]`.
- **Resilient PHP** — per-handler failure isolation (each subscriber gets its own copy of the message; one failing handler doesn't abort siblings or trigger sibling re-runs), `RetryTemplateBuilder` retry policies at the channel level, DBAL-backed dead-letter queue with replay, `#[Deduplicated]` idempotency, OpenTelemetry spans on every handler, automatic correlation and causation propagation.

## Key Features

- **Durable workflow primitives**: `#[Saga]` for stateful coordina
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=ecotone.tech · GET /v1/domain/ecotone.tech · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for ecotone.tech:
1. POST https://agentwebmap.com/v1/sites/ecotone.tech/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://ecotone.tech/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/ecotone.tech/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/ecotone.tech).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.