README

gRPC bridge (without the official Temporal PHP SDK) to persist the Durable journal in a minimal Temporal workflow.

Read-only mirror. This repository is a subtree-split of gplanchat/durable-dev, published so Composer can require this package on its own. Issues and pull requests are disabled here — open them on the monorepo.

The tests are in the monorepo, not here. This split carries source only. What covers it is tests/unit/Bridge/Temporal/ in the monorepo, run by its unit suite.

Documentation: durable.rocks.

PHP namespace: Gplanchat\Bridge\Temporal.

Deployment invariant: when Temporal is enabled for Durable, the journal (EventStore) and application queues share the same Temporal connection (temporal://…). What a transport does is selected by its purpose — journal, application, activity_worker or nexus_worker, see Transport purposes — given as options.purpose or ?purpose= in the DSN, or inferred: an inner DSN means application, nothing means journal. Schemes temporal-journal:// and temporal-application:// are still accepted and normalized to temporal://.

Requirements

• PHP ext-grpc
• A reachable Temporal frontend (e.g. host:7233)

Components

Transport DSN (single scheme)

temporal://127.0.0.1:7233?namespace=default&journal_task_queue=durable-journal&tls=0

Query parameters: namespace, task_queue or journal_task_queue, workflow_type, workflow_task_queue, activity_task_queue, nexus_task_queue, identity, tls (bool), inner, purpose. Unknown keys are ignored today (a typo falls back to the default silently — issue #353 makes them fail).

Transport purposes

One factory, four transports. The purpose decides which one a temporal:// DSN builds; the last column is the setup error the factory throws when the wiring it needs is missing, and what to do about it.

Any other value fails with Unknown temporal purpose "…", expected journal, application, activity_worker, or nexus_worker.

The three receive-only transports do their work inside get() and hand nothing to the Messenger worker, so retry_strategy, failure_transport and messenger:consume --limit have no effect on them: retries are the server's retry policy, and a failed poll is retried by the next get(). A worker deployment typically consumes the three at once:

framework:
    messenger:
        transports:
            durable_temporal_journal:
                dsn: '%env(DURABLE_DSN)%'
            durable_temporal_activity:
                dsn: '%env(DURABLE_DSN)%'
                options: { purpose: activity_worker }
            durable_temporal_nexus:
                dsn: '%env(DURABLE_DSN)%'
                options: { purpose: nexus_worker }

bin/console messenger:consume durable_temporal_journal durable_temporal_activity durable_temporal_nexus

Journal (receive-only)

Without inner and without options.purpose=application, the transport is TemporalJournalTransport.

Application queues (inner)

temporal://127.0.0.1:7233?namespace=default&inner=in-memory://&workflow_task_queue=durable-workflows&activity_task_queue=durable-activities&tls=0

Or temporal://… without inner in the URL and options: { purpose: application, inner: 'in-memory://' } in Messenger config.

• inner (required for application mode): DSN of the real Symfony Messenger transport (Redis, Doctrine, in-memory, etc.).
• workflow_task_queue / activity_task_queue: used for gRPC evolution; while the envelope delegates to inner, application traffic uses that inner transport.

Symfony

1. In the monorepo the code lives under src/Bridge/Temporal; in a split repo: composer require gplanchat/durable-bridge-temporal.
2. Register Gplanchat\Bridge\Temporal\TemporalBridgeBundle in the kernel.
3. framework.messenger.transports.<name>: 'temporal://…' (without inner, journal DSN — e.g. journal_task_queue=durable-journal).
4. messenger:consume <name> (standard Symfony worker; poll and journal task handling are inside TemporalJournalTransport::get()). Add an activity_worker transport for the activities and, if the application serves operations, a nexus_worker one — see Transport purposes.
5. Wire EventStoreInterface to TemporalJournalEventStore where appropriate (explicit DI).

FrankenPHP worker

Same idea as messenger:consume: run the Messenger worker under FrankenPHP worker mode (or systemd) with messenger:consume <journal_transport> pointing at temporal://… without inner.

License

MIT — see LICENSE in this directory and WA004.

Further reading

• DUR019 — Temporal gRPC bridge and journal: documentation/adr/DUR019-temporal-grpc-bridge-and-journal.md