Weave Code
Framework Laravel Package
spiral/framework
Spiral Framework is a high-performance, long-running full-stack PHP framework built for RoadRunner. PSR-compliant components, resident memory kernel, and native support for queues, GRPC, WebSockets, and background workers.
Spiral, High-Performance PHP/Go Framework
Frequently asked questions about Framework
- Can Spiral Framework replace Laravel for high-traffic APIs without rewriting the entire app?
- Yes, Spiral supports incremental migration. Start by replacing Laravel’s queue system or HTTP layer with Spiral’s RoadRunner-powered alternatives, then gradually adopt other components like Cycle ORM or gRPC support. The framework’s bootloaders (similar to Laravel’s service providers) ease the transition.
- How does Spiral’s performance compare to Laravel’s optimized setups (e.g., OPcache, JIT)?
- Spiral consistently outperforms Laravel in benchmarks (e.g., Techempower) due to its resident-memory kernel and RoadRunner integration, offering ~2x faster HTTP responses. It’s ideal for latency-sensitive applications but requires PHP 8.2+ and RoadRunner setup.
- What are the risks of migrating from Laravel’s Eloquent ORM to Spiral’s Cycle ORM?
- Cycle ORM is schema-first (like Laravel migrations) but lacks Eloquent’s active-record syntax. You’ll need to refactor models and queries, though it supports multi-database and NoSQL backends. Test thoroughly, as data access patterns may require significant changes.
- Does Spiral support Laravel’s Blade templating engine, or do I need to switch to Twig/Stempler?
- Spiral doesn’t natively support Blade. You’ll need to migrate to Stempler (custom tags) or Twig. Blade templates can be converted manually or via third-party tools, but this adds effort to the migration process.
- How does Spiral handle background jobs compared to Laravel’s queue system?
- Spiral’s queue system integrates with RoadRunner for supervision, leak safety, and high concurrency. It supports AMQP, SQS, Kafka, and more, but job processing logic (e.g., retries, timeouts) may differ from Laravel’s queue workers. Use Spiral’s queue components for native integration.
- Are there Laravel-specific packages (e.g., Cashier, Scout) with Spiral alternatives?
- Spiral lacks direct replacements for Laravel’s ecosystem packages. For payments, consider Stripe’s PHP SDK or Spiral’s payment components. For search, use Elasticsearch or Spiral’s data-grid tools. Evaluate alternatives case-by-case, as some may require custom development.
- What’s the learning curve for a Laravel developer adopting Spiral’s bootloaders and RoadRunner?
- Moderate to steep. Spiral’s bootloaders (like service providers) are familiar, but RoadRunner’s process management (workers, pools) and PSR-compliant architecture (e.g., interceptors) require new concepts. Start with Spiral’s docs and Discord community for guidance.
- Can Spiral run in shared hosting environments, or is it limited to VPS/Docker/Kubernetes?
- Spiral is designed for server environments supporting RoadRunner (PHP 8.2+, Docker, Kubernetes, or VPS). Shared hosting with PHP-FPM/Nginx won’t work natively. Use Docker or cloud platforms like AWS ECS for production deployments.
- How does Spiral handle real-time features like WebSockets compared to Laravel Echo/Pusher?
- Spiral’s WebSocket support is built into RoadRunner, offering native, high-performance connections without relying on third-party services like Pusher. It integrates seamlessly with Spiral’s queue and gRPC systems for full-stack real-time apps.
- What testing tools or frameworks does Spiral provide for unit/integration testing?
- Spiral includes built-in testing utilities and supports PHPUnit, Pest, and Symfony’s PHPUnit Bridge. It also offers observability tools like OpenTelemetry for monitoring long-running processes. Existing Laravel tests may need adjustments for Spiral’s architecture.
Weaver
How can I help you explore Laravel packages today?