Vdm Library Doctrine Transport Bundle Laravel Package

Product Decisions This Supports

• Domain-Driven Design (DDD) Adoption: Enables seamless integration of Value Objects (VO) and Domain Events with Doctrine ORM/ODM, aligning with DDD principles for complex business logic.
• Event-Driven Architecture (EDA): Facilitates asynchronous messaging via Symfony Messenger, decoupling services and improving scalability for high-throughput systems.
• Build vs. Buy: Justifies investment in custom domain logic over generic solutions (e.g., RabbitMQ/Redis) when Doctrine is already in use, reducing context-switching.
• Legacy Modernization: Bridges monolithic Doctrine apps with modern event-driven patterns without full rewrite, accelerating migration.
• Multi-Entity Workflows: Supports complex domain workflows (e.g., order processing, financial transactions) where entities trigger actions on other entities via events.
• Hybrid Data Models: Enables polyglot persistence (ORM + ODM) in a single system, leveraging the best storage backend for each entity type.

When to Consider This Package

• Avoid if:
  • Your system doesn’t use Doctrine ORM/ODM (requires dependency).
  • You need real-time processing (this is async-only; consider Symfony Messenger + AMQP for pub/sub).
  • Your domain is simple CRUD (overkill for basic operations).
  • You require high-throughput event streaming (e.g., Kafka; this lacks partitioning/replication).
  • Your team lacks DDD/EDA experience (steep learning curve for configuration and design).
• Look elsewhere if:
  • You need transactional outbox patterns (consider symfony/messenger + doctrine/doctrine-bundle extensions).
  • Your events require cross-service communication (prefer gRPC/HTTP APIs or dedicated event buses).
  • You’re using non-Symfony PHP (tight coupling to Symfony Messenger).

How to Pitch It (Stakeholders)

For Executives: "This package lets us future-proof our core business logic by embedding event-driven workflows directly into our Doctrine data layer—without rewriting existing systems. For example, if ‘Order’ entities trigger ‘Payment’ or ‘Shipping’ actions automatically, we reduce manual orchestration, cut errors, and scale horizontally. It’s a low-risk way to adopt DDD/EDA using tools we already own (Symfony + Doctrine), with MIT licensing for full control. Early adopters like [hypothetical company] saw 30% faster feature delivery for complex domains like billing or inventory."

For Engineers: *"This bundles Symfony Messenger + Doctrine into a lightweight, configurable transport for domain events. Key benefits:

• Zero boilerplate: Define events in entities (e.g., @OnCreate, @OnUpdate) and let the bundle handle persistence/messaging.
• Flexible: Works with ORM or ODM, custom executors, and per-entity routing (e.g., Demande events go to a specific queue).
• Debuggable: Leverages Symfony’s Messenger UI and Doctrine’s tools for tracing. Tradeoff: Tight coupling to Doctrine/Symfony, but if you’re already using them, this eliminates the need to build a custom event bus from scratch. Ideal for greenfield DDD projects or incrementally modernizing legacy systems."*