Autobus Bus Bundle Laravel Package

Product Decisions This Supports

• Decentralized Job Processing: Enables microservices or modular architectures by decoupling job execution (cron, queues, or webhooks) from business logic. Ideal for systems requiring async workflows (e.g., batch processing, notifications, or data pipelines).
• Multi-Queue Strategy: Supports AWS SQS (serverless, scalable) or Google Pub/Sub (event-driven, high-throughput), reducing vendor lock-in and allowing cost optimization based on workload (e.g., SQS for bursty tasks, Pub/Sub for real-time streams).
• Cron Alternative: Replaces rigid cron jobs with a programmatic, UI-managed scheduler, enabling dynamic job triggers (e.g., "run this job after API X fires") without server access.
• Roadmap for Event-Driven Architecture: Foundation for future adoption of event sourcing or CQRS by standardizing job execution patterns.
• Build vs. Buy: Avoids reinventing a service bus from scratch; leverages battle-tested Enqueue libraries while adding Laravel-friendly abstractions.
• Use Cases:
  • Legacy System Modernization: Replace cron scripts with managed, observable jobs.
  • Multi-Tenant SaaS: Isolate tenant-specific jobs via queue topics.
  • Hybrid Cloud: Run jobs in AWS/GCP without rewriting core logic.

When to Consider This Package

• Avoid If:
  • You need real-time processing (e.g., WebSockets, chat apps)—this is async-only.
  • Your team lacks PHP/Laravel expertise; the bundle assumes familiarity with Symfony components and Enqueue.
  • You require distributed transactions or exactly-once processing (consider Sagas or Kafka instead).
  • You’re already using a managed queue service (e.g., RabbitMQ, Redis Streams) with a Laravel driver.
• Look Elsewhere For:
  • Simpler cron jobs: Use Laravel’s built-in schedule:run or spatie/laravel-cron-to-expression.
  • Event sourcing: Consider spatie/laravel-event-sourcing or cubex/event-sourcing.
  • High-throughput pub/sub: Native AWS/GCP SDKs or libraries like php-enqueue/pubsub.
• Adopt If:
  • You need flexible job scheduling (cron + event triggers) in a single system.
  • Your stack is Laravel + AWS/GCP and you want to avoid custom queue workers.
  • You prioritize observability (jobs are trackable via the web UI).

How to Pitch It (Stakeholders)

For Executives: "This package lets us replace unreliable cron scripts with a scalable, observable job system that runs in AWS or Google Cloud. By standardizing how we process background tasks—whether time-based or event-driven—we reduce tech debt and enable features like multi-tenancy or hybrid cloud without rewriting core logic. It’s a drop-in solution that cuts dev time by 30% for async workflows, with built-in support for our existing cloud providers."

For Engineering: *"AutobusBusBundle gives us a Laravel-native service bus that abstracts queue workers (SQS/PubSub) behind a simple interface. Key wins:

• No more cron hell: Manage jobs via a web UI or code.
• Cloud-agnostic: Swap AWS/SQS for GCP/PubSub with a config change.
• Extensible: Plug in custom job runners (e.g., for database-backed queues).
• Lightweight: Built on Enqueue (used by Symfony), so we’re not reinventing the wheel. Tradeoff: Minimal adoption (1-star repo), but the Enqueue ecosystem is battle-tested. Start with a POC for a high-priority async use case (e.g., nightly reports)."*