Broadway Saga Laravel Package

Product Decisions This Supports

• Distributed Transaction Management: Enables reliable, long-running workflows across microservices without two-phase commit (2PC), addressing a critical gap in event-driven architectures.
• Eventual Consistency: Supports use cases requiring strong consistency guarantees (e.g., financial transactions, inventory reservations) while leveraging async processing.
• Roadmap for Resilience: Justifies investment in a robust event-sourcing backbone (Broadway) by adding sagas for complex workflows, reducing custom error-handling code.
• Build vs. Buy: Avoids reinventing saga orchestration from scratch, accelerating time-to-market for workflow-heavy features (e.g., order fulfillment, multi-step approvals).
• Use Cases:
  • E-commerce: Order processing with inventory, payment, and shipping steps.
  • Fintech: Cross-service transactions (e.g., transfers, reconciliations).
  • Logistics: Multi-step shipment coordination (pickup → transit → delivery).
  • Healthcare: Patient record updates across disparate systems.

When to Consider This Package

• Adopt if:
  • Your system uses Broadway for event sourcing and needs saga support.
  • Workflows require compensating actions (rollbacks) for failed steps.
  • Teams prioritize developer productivity over custom saga implementations.
  • You’re not using a dedicated workflow engine (e.g., Camunda, Temporal) but need lightweight orchestration.
• Look Elsewhere if:
  • Your stack isn’t PHP/Laravel or lacks Broadway integration.
  • Workflows are simple (linear, no rollback needs) → use native Laravel jobs.
  • You need human-in-the-loop approvals → consider Camunda or Zeebe.
  • High scalability is critical → evaluate Temporal or Step Functions.
  • Last release (2020) is a blocker; active maintenance is required.

How to Pitch It (Stakeholders)

Executives: "This package lets us handle complex, multi-service workflows reliably—like processing orders or financial transactions—without building custom orchestration. It integrates seamlessly with our existing event-sourcing architecture (Broadway), reducing risk and accelerating delivery of critical features. Think of it as ‘Git for workflows’: versioned, auditable, and resilient to failures."

Engineering: *"Broadway Saga gives us a battle-tested way to manage sagas (choreography pattern) with compensating transactions. Key benefits:

• No 2PC: Avoids distributed locks; uses events for coordination.
• Idempotency: Built-in retries and rollbacks for failed steps.
• Laravel-native: Works with queues, events, and existing infrastructure. Tradeoff: Last updated in 2020, but the core pattern is stable. We’d need to vet for PHP 8.x compatibility and evaluate maintenance risks vs. rewrite effort."*

Architects: *"This fills a gap in our event-driven toolkit by providing saga orchestration without coupling to a heavy workflow engine. Ideal for:

• Internal consistency: Ensuring all steps of a workflow (e.g., payment + inventory) succeed or roll back atomically.
• Observability: Broadway’s event store lets us replay/redebug sagas. Caveats: No native support for external systems (e.g., SAP); would need adapters. Consider pairing with Laravel Horizon for monitoring."*