Autobus Bus Sample Bundle Laravel Package

Product Decisions This Supports

• Event-Driven Architecture (EDA) Adoption: Accelerates implementation of a bus-based event system (e.g., CQRS, microservices, or decoupled services) without reinventing the wheel. Reduces dev time for event publishing/subscription patterns.
• Roadmap for Scalability: Enables modular event handling for future-proofing monolithic apps or transitioning to microservices. Aligns with "build vs. buy" by avoiding custom event bus solutions.
• Use Cases:
  • Real-time notifications (e.g., user actions triggering alerts).
  • Decoupled workflows (e.g., order processing → inventory → shipping).
  • Legacy system integration via event bridges.
• Tech Stack Alignment: Leverages Symfony/Laravel ecosystems, reducing friction for PHP teams already using these frameworks.

When to Consider This Package

• Adopt if:

  • Your team needs a lightweight, PHP-native event bus with minimal setup (Symfony/Laravel compatibility).
  • You’re building event-driven features but lack time/resources for a custom solution.
  • Your stack includes PHP 7.0+, Symfony, or Laravel (or you’re willing to integrate it via Symfony’s bundle system).
  • You prioritize MIT-licensed, open-source over proprietary tools.

• Look elsewhere if:

  • You need high-throughput, distributed event processing (consider Kafka, RabbitMQ, or Laravel’s built-in queue workers).
  • Your team lacks Symfony/Laravel familiarity (steep learning curve for integration).
  • You require enterprise-grade support (this is a community package with no stars/dependents).
  • You’re using non-PHP languages (e.g., Node.js, Go) or need cross-language event buses.

How to Pitch It (Stakeholders)

For Executives: "This package lets us rapidly implement event-driven workflows—like a ‘fire-and-forget’ messaging system for our PHP apps—without heavy infrastructure costs. Think of it as plug-and-play glue for decoupling services, reducing technical debt, and enabling real-time features (e.g., notifications, workflows) faster. It’s MIT-licensed, so no vendor lock-in, and integrates seamlessly with our existing Laravel/Symfony stack."

For Engineering: *"AutobusBusSampleBundle gives us a Symfony bundle to standardize event publishing/subscription across the app. It’s a lightweight alternative to writing custom event handlers or relying on queues alone. Key benefits:

• Reduces boilerplate: Handles event dispatching/routing out of the box.
• Future-proof: Supports complex event flows (e.g., retries, middleware) if we scale.
• Low risk: MIT license, minimal dependencies, and PHP 7.0+ compatible. Tradeoff: Not for high-volume systems, but perfect for internal event coordination or prototyping."*

For Developers: *"If you’re tired of manually wiring up event listeners or using queues for everything, this bundle lets you declare events as services and let the framework handle the rest. Example:

// Publish an event
$bus->dispatch(new UserRegisteredEvent($user));

// Subscribe to it
$bus->subscribe(UserRegisteredEvent::class, function ($event) {
    // Handle logic here
});

It’s like Laravel’s events, but with Symfony bundle structure and potential for more advanced routing."*