Keda Bundle Laravel Package

Product Decisions This Supports

• Automated Scaling for Event-Driven Workloads: Enables PHP-based definition of KEDA (Kubernetes Event-Driven Autoscaler) CRDs, allowing teams to declaratively define event-driven scaling policies (e.g., scaling based on Kafka messages, RabbitMQ queues, or HTTP requests) without deep Kubernetes expertise. Aligns with roadmaps for serverless, event-driven architectures, or microservices.
• Build vs. Buy: Avoids reinventing KEDA integration from scratch, reducing devops overhead while maintaining flexibility. Ideal for teams already using Laravel/PHP in Kubernetes environments.
• Developer Experience (DX): Reduces cognitive load for backend engineers by letting them define scaling rules in PHP (e.g., via annotations or config files) instead of YAML. Supports teams adopting GitOps or Infrastructure-as-Code (IaC) with PHP-centric workflows.
• Use Cases:
  • Event-Driven Microservices: Scale PHP-based consumers (e.g., queue processors) dynamically based on workload.
  • Hybrid Cloud/Edge: Deploy PHP apps in Kubernetes clusters (e.g., AWS EKS, GKE) with auto-scaling tied to custom events.
  • Legacy Modernization: Gradually migrate monoliths to event-driven architectures by scaling specific components independently.
  • CI/CD Integration: Generate KEDA manifests as part of PHP-based deployment pipelines (e.g., Laravel Forge, Envoyer).

When to Consider This Package

• Adopt if:

  • Your team uses Laravel/PHP and deploys to Kubernetes (EKS, GKE, AKS, etc.).
  • You need event-driven autoscaling (e.g., scale workers based on queue depth, HTTP traffic, or custom metrics).
  • Your devops team prefers PHP-native configurations over YAML for KEDA CRDs.
  • You’re building serverless-like PHP applications with dynamic scaling needs.
  • Your roadmap includes GitOps/IaC with PHP-based tooling (e.g., Laravel + Kubernetes).

• Look elsewhere if:

  • You’re not using Kubernetes (KEDA is Kubernetes-specific).
  • Your scaling needs are static or managed via Horizontal Pod Autoscaler (HPA) or Cluster Autoscaler.
  • Your team lacks PHP/Kubernetes familiarity (steep learning curve for CRDs and KEDA concepts).
  • You require advanced KEDA features (e.g., custom metrics adapters) not yet supported by this bundle.
  • You’re in a highly regulated environment where PHP-based CRD definitions introduce compliance risks (e.g., auditability of YAML vs. code).

How to Pitch It (Stakeholders)

For Executives: "This package lets our PHP teams define Kubernetes autoscaling rules in Laravel—no YAML, no devops bottlenecks. Imagine scaling our queue workers or API endpoints dynamically based on real-time events (e.g., orders, notifications) without manual intervention. It’s a force multiplier for our event-driven architecture roadmap, reducing cloud costs by scaling only what’s needed. Low risk: leverages battle-tested KEDA under the hood, with PHP as the familiar interface."

For Engineering/DevOps: *"The keda-bundle lets you define KEDA ScaledObjects and Triggers in PHP (e.g., via Laravel config or annotations), so your backend teams can own scaling logic. Key benefits:

• Faster iterations: No context-switching to YAML for scaling rules.
• Consistency: Scaling policies live alongside your PHP code (version-controlled, tested).
• Flexibility: Supports all KEDA scalers (e.g., Kafka, RabbitMQ, Prometheus) out of the box.
• Future-proof: Aligns with our Kubernetes strategy while keeping the door open for custom metrics adapters later. Tradeoff: Early-stage (0 stars), but KEDA is production-grade—this is just a PHP wrapper. Start with a pilot for a non-critical microservice (e.g., a background job processor)."*

For Developers: *"Tired of writing YAML for KEDA? This bundle lets you define scaling rules in PHP. For example:

// In a Laravel service provider or config file
Keda::scaledObject('php-worker')
    ->group('keda.sh')
    ->kind('ScaledObject')
    ->cooldownPeriod('30s')
    ->minReplicaCount(1)
    ->maxReplicaCount(10)
    ->trigger('rabbitmq', [
        'queue' => 'orders',
        'auth' => 'amqp://user:pass@rabbitmq:5672',
    ]);

Now your queue workers scale automatically when orders pile up—no Kubernetes expertise required. Perfect for Laravel apps on Kubernetes!"*