Framework Laravel Package

Product Decisions This Supports

• High-Performance Microservices & APIs: Leverage Spiral’s RoadRunner integration and resident memory kernel to build ultra-low-latency microservices (e.g., real-time analytics, IoT pipelines, or high-frequency trading systems). The GRPC/HTTP2 support enables seamless inter-service communication, reducing coupling vs. REST.

• Event-Driven & CQRS Architectures: Adopt Spiral’s Pub/Sub, Queue supervision, and Temporal workflows to replace legacy event buses (e.g., RabbitMQ + custom workers). Ideal for order processing, notifications, or saga patterns where reliability and retries are critical.

• Replace Laravel/Symfony for High-Scale Apps: If your roadmap includes PCI-compliant systems (e.g., payments, healthcare) or CLI-heavy workflows (e.g., batch processing), Spiral’s anti-memory-leak tools and native queue workers outperform traditional PHP frameworks. Benchmark against TechEmpower to justify the switch.

• Internal Developer Platform (IDP) for PHP: Use Spiral’s scaffolding and prototype injector to accelerate team onboarding. Generate boilerplate (controllers, jobs, bootloaders) via CLI, reducing dev time by 30–50% for repetitive tasks (e.g., CRUD APIs, background jobs).

• Hybrid PHP/Go Workloads: For mixed-language stacks, Spiral’s Go-compatible components (via RoadRunner) let you offload CPU-heavy tasks (e.g., image processing, ML inference) to Go while keeping business logic in PHP. Reduces cloud costs vs. monolithic Go/Python.

When to Consider This Package

• Avoid if:

  • Your team lacks PHP 8.1+ expertise or prefers Laravel/Symfony ecosystems (Spiral’s learning curve is steeper).
  • You need out-of-the-box admin panels (Spiral requires custom scaffolding; consider Filament or Backpack for Laravel).
  • Your app is simple CRUD with no async/real-time needs (overkill vs. Laravel + Inertia.js).
  • You’re locked into AWS Lambda (Spiral’s RoadRunner is optimized for long-lived processes, not serverless).

• Consider if:

  • You’re building high-throughput systems (e.g., >10K RPS) where memory efficiency matters.
  • Your stack requires GRPC, WebSockets, or Temporal workflows (no native Laravel/Symfony support).
  • You need fine-grained dependency injection (e.g., isolated scopes for microservices) or PSR-16 caching at scale.
  • Your team values performance over conventions (e.g., no magic methods, explicit configuration).

How to Pitch It (Stakeholders)

For Executives:

"Spiral Framework lets us build PHP systems that rival Go/Java in performance—without rewriting our stack. For example:

• Cost savings: RoadRunner’s resident memory cuts cloud bills by 40% vs. Laravel + Queue workers (no cold starts).
• Scalability: Handled 20K concurrent WebSocket connections in load tests (vs. Laravel’s ~5K limit).
• Future-proof: Built-in Temporal workflows let us replace AWS Step Functions with open-source PHP, reducing vendor lock-in. We’re proposing a 3-month pilot for our [highest-latency service], with a goal to reduce API response times by 60% and cut DevOps overhead by 25%."

For Engineering:

"Spiral gives us:

• RoadRunner: Replace Supervisor + PHP-FPM with a single process manager for queues, HTTP, and WebSockets. No more zombie processes.
• Cycle ORM: A type-safe, query-builder-free alternative to Eloquent that scales to 10M+ rows (used by Spiral Scout).
• CLI Superpowers: Generate entire modules (controllers, jobs, bootloaders) in seconds via spiral scaffold. Example:

  spiral scaffold:controller User --namespace=App\\Api\\V1 --methods=index,store
  

• Debugging: Built-in tokenizers and isolated IoC scopes make dependency leaks obvious at compile time (vs. runtime errors in Laravel). Tradeoff: Steeper learning curve, but we’ll onboard with a 2-week deep dive and pair with Spiral’s Discord community."*

For Architects:

"Key differentiators vs. Laravel/Symfony:

Call to Action: "Let’s prototype a Spiral microservice for [X use case] and compare it to our current stack. I’ll provide a 1-pager with benchmarks and migration steps by [date]."