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.
High-Performance PHP Framework
Frequently asked questions about Framework
- Can Spiral Framework replace Laravel’s core for high-performance APIs?
- Yes, Spiral can replace Laravel’s core for APIs by leveraging RoadRunner’s resident memory kernel and Cycle ORM for type-safe queries. Use the RoadRunner Bridge to run Laravel’s HTTP kernel under RoadRunner, reducing cold starts and improving concurrency. Start with incremental adoption—replace PHP-FPM/Nginx first, then migrate models to Cycle ORM for bulk operations.
- How does Spiral’s Cycle ORM compare to Laravel’s Eloquent for performance?
- Cycle ORM outperforms Eloquent in bulk operations and complex joins due to its type-safe query builder and lower overhead. However, it lacks Eloquent’s active record convenience, requiring model rewrites for existing applications. Use Cycle for read-heavy workloads while keeping Eloquent for simpler CRUD operations during a phased migration.
- Is Spiral Framework compatible with Laravel’s existing queue system?
- Spiral extends Laravel’s queue system with AMQP, Kafka, and Beanstalk backends via bridges, improving reliability for distributed jobs. Existing Laravel queues (database, sync) will still work, but Spiral’s native queue support is better suited for high-throughput or event-driven architectures. Test queue workers under RoadRunner to ensure compatibility with Spiral’s process model.
- What Laravel versions does Spiral Framework support for integration?
- Spiral Framework integrates with Laravel 8.x and 9.x via PSR-11 containers and middleware bridges, but full compatibility depends on your use case. For HTTP routing or DI, use the RoadRunner Bridge; for ORM, Cycle ORM requires model rewrites. Check the [Spiral-Laravel documentation](https://spiral.dev/docs) for version-specific guides, as Spiral’s core is framework-agnostic.
- How do I deploy a Laravel app with Spiral’s RoadRunner for production?
- Deploy Laravel under RoadRunner by replacing PHP-FPM with the RoadRunner worker. Use Docker for containerized deployments, as RoadRunner manages processes natively. Configure `roadrunner.yml` to handle HTTP, queues, and WebSockets, then map Laravel’s Artisan commands to Spiral’s console. Monitor memory usage with RoadRunner’s built-in supervision tools to prevent leaks.
- Are there alternatives to Spiral Framework for Laravel performance optimization?
- For Laravel-specific optimizations, consider Laravel Octane (Swoole/Preact) for HTTP performance or Laravel Horizon for queue scaling. Spiral’s advantage lies in its hybrid runtime (RoadRunner + resident memory) and Cycle ORM, which are harder to replicate without a full rewrite. If you need real-time features (WebSockets/GRPC), Spiral’s native support is unmatched in PHP.
- How does Spiral handle real-time features like WebSockets in Laravel?
- Spiral natively supports WebSockets via RoadRunner, eliminating the need for Pusher/Laravel Echo. Use the RoadRunner Bridge to integrate WebSocket routes into your Laravel app, then leverage Spiral’s event-driven architecture for scalable real-time updates. Test with Spiral’s built-in WebSocket clients to ensure compatibility with Laravel’s Blade or API responses.
- Can I use Spiral Framework alongside Laravel’s Blade templating?
- Yes, Spiral supports dynamic templates (Twig) and can coexist with Blade via custom loaders or middleware. For a seamless experience, use Spiral’s HTTP layer to serve Blade views while offloading heavy logic to Spiral’s services. Avoid mixing Blade and Spiral’s templating systems in the same view hierarchy to prevent conflicts.
- What’s the learning curve for migrating from Laravel to Spiral?
- The learning curve depends on your team’s familiarity with PSR-11 containers, RoadRunner, and Cycle ORM. Start with Spiral’s HTTP layer (RoadRunner Bridge) and gradually adopt Cycle ORM or DI. Spiral’s documentation and Discord community offer migration guides, but expect 2–4 weeks for a small team to ramp up on core concepts like bootloaders and resident memory.
- How does Spiral Framework handle testing compared to Laravel’s Pest/Dusk?
- Spiral uses PHPUnit with its own console commands for testing, but you can integrate Pest via custom test runners. For Dusk (browser testing), use Spiral’s HTTP layer to mock routes and leverage Laravel’s testing helpers. Spiral’s bootloaders can be configured to load Laravel’s service providers during tests, ensuring compatibility with existing test suites.
Weaver
How can I help you explore Laravel packages today?