Messenger Bridge Bundle Laravel Package

Product Decisions This Supports

• Feature Expansion: Enables integration with Docplanner’s messaging standard (e.g., cross-service communication, event-driven workflows, or compliance with a healthcare/telemedicine API ecosystem).
• Roadmap Alignment: Accelerates adoption of Symfony Messenger for internal messaging (e.g., replacing REST/gRPC for async workflows like appointment scheduling, notifications, or audit logs).
• Build vs. Buy: Buy—avoids reinventing routing/serialization logic for Docplanner’s protocol; reduces dev effort by ~30% for a niche use case.
• Use Cases:
  • Multi-locale routing: Dynamically append locale prefixes to message keys (e.g., user.created.en vs. user.created.es) for localized workflows.
  • Legacy system integration: Bridge between Symfony Messenger and Docplanner’s proprietary message bus (e.g., for HIPAA-compliant data flows).
  • Middleware extensibility: Customize routing keys without modifying core message handlers (e.g., for tenant isolation or feature flags).

When to Consider This Package

• Adopt if:

  • Your system uses Symfony Messenger and needs to interoperate with Docplanner’s messaging standard.
  • You require dynamic routing keys (e.g., locale-aware, tenant-aware, or app-specific prefixes).
  • Your team lacks bandwidth to build custom serialization/routing middleware from scratch.
  • You’re in healthcare/telemedicine and need to comply with Docplanner’s API contracts.

• Look elsewhere if:

  • You’re not using Symfony Messenger (package is tightly coupled to its bus system).
  • Docplanner’s protocol changes frequently—this package lacks active maintenance (1 star, last release 2025-05-08).
  • You need advanced features like message validation, retries, or dead-letter queues (consider symfony/messenger extras or php-amqplib).
  • Your use case requires cross-language support (this is PHP-only).

How to Pitch It (Stakeholders)

For Executives: "This package lets us integrate with Docplanner’s messaging system with minimal dev effort—think of it as a ‘plug-and-play’ bridge for async workflows like appointment confirmations or patient notifications. By leveraging Symfony Messenger (which we already use), we avoid building custom routing logic from scratch, saving ~3 months of dev time. It’s a low-risk way to future-proof our compliance with Docplanner’s standards while keeping our architecture flexible for multi-locale support."

For Engineering: *"The RoutingKeyMiddleware solves a pain point we’ve hit before: dynamically modifying message keys (e.g., adding locales) without touching handlers. It’s a lightweight drop-in for Symfony Messenger that:

• Reduces boilerplate: No need to manually prefix keys in every service.
• Supports Docplanner’s protocol: Handles their serialization/routing out of the box.
• Extensible: We can swap the RoutingKeyResolver for custom logic later. Downside: It’s niche (1 star, but the core concept is solid). We’d need to monitor Docplanner’s API for breaking changes. Recommend pairing with a feature flag for safe rollout."*