Weave Code
Thruway Bundle Laravel Package
voryx/thruway-bundle
Symfony bundle integrating Thruway, a WAMP v2 client/router, to add real-time RPC and Pub/Sub to Symfony apps. Expose PHP services over WebSocket, publish and subscribe to events, and build reactive features with minimal configuration.
Bundle for building Real-time Apps in Symfony
Frequently asked questions about Thruway Bundle
- Is voryx/thruway-bundle a Laravel package?
- No. voryx/thruway-bundle is a Symfony 2 bundle that integrates the Thruway WAMP v2 client and router into Symfony's dependency injection container, event dispatcher, and console commands. It has no Laravel service provider, facade, or publishable config. For Laravel teams it is useful only as an architecture reference, not as an installable dependency.
- Can I install voryx/thruway-bundle in a Laravel app with Composer?
- You should not expect it to install cleanly in a modern Laravel application. The bundle assumes a Symfony kernel, compiler passes, services.yml, and long-running console workers, none of which have Laravel analogues. Its 2019 release also carries framework and PHP constraints that will likely conflict with current Laravel requirements. Composer resolution will probably fail before you can evaluate it.
- What does voryx/thruway-bundle actually do?
- It wires the Thruway WAMP v2 client, built on Ratchet, into Symfony so PHP services can be exposed over WebSocket for RPC and topic-based publish/subscribe. It demonstrates realms, transports, service registration, session authentication hooks, and long-running worker processes. The reusable value for a Laravel evaluation is that conceptual model, not the bundle code itself.
- Does ThruwayBundle support Laravel 10, Laravel 11, or PHP 8.1 and above?
- There is no evidence of support for modern Laravel versions or PHP 8.1 and above. The last release was in July 2019 and targets Symfony 2, which is end of life and no longer receives security patches. A current PHP 8.x requirement alone is likely enough to disqualify the bundle. Treat any claim of Laravel compatibility as unsupported.
- What are Laravel alternatives to ThruwayBundle for realtime RPC and pub/sub?
- For most Laravel use cases, use Laravel broadcasting with Reverb, Pusher, or Soketi for server-to-client events. If you genuinely need WAMP v2, drive a maintained WAMP client directly inside an Octane or queue worker rather than trying to port this bundle. For bidirectional RPC, evaluate Laravel Octane with WebSockets or a dedicated realtime service. The WAMP ecosystem is small, so weigh hiring and tooling costs against simpler transports.
- Is WAMP2 overkill for simple server-to-client push in Laravel?
- Usually yes. If your requirement is one-way fan-out from server to browser, Laravel broadcasting, Server-Sent Events, or plain WebSockets are simpler and better supported. WAMP v2 earns its complexity when you need bidirectional RPC, realms, router-level authentication, and polyglot services exchanging calls and topics. Confirm whether WAMP2 is a hard external contract before adopting it.
- How do you expose Symfony services over WebSocket with ThruwayBundle?
- The bundle registers PHP services with the WAMP router through Symfony container configuration and attributes, then runs router and worker processes via console commands. Those workers are long-running, so lifecycle and failure handling differ from normal request-response PHP. This pattern does not transfer directly to Laravel because there is no bundle class, compiler pass, or Symfony console wiring. In Laravel you would need to rebuild the equivalent worker and registration layer yourself.
- Is voryx/thruway-bundle maintained and safe for production?
- The project shows negligible maintenance signal: the last release was 2019-07-04, it has roughly 98 stars, and zero dependents. There is no evident security response path, and upstream Symfony 2 is out of support. That combination is high risk for any new production system. It should not be represented to stakeholders as a shippable dependency for a current Laravel stack.
- Can I fork ThruwayBundle or port it to Laravel?
- Forking is technically possible but means owning the bundle, the Thruway client, and its Ratchet dependency indefinitely. Porting it would require replacing Symfony container wiring, console commands, and event hooks with Laravel service providers, workers, and events, which forfeits most of the bundle's original contribution. For a greenfield Laravel build, substitution with a Laravel-native transport is almost always cheaper. Keep a fork only if WAMP2 is a hard contractual requirement.
- How should I migrate off ThruwayBundle to a supported realtime stack?
- If an existing Symfony 2 application uses this bundle, stand up the WAMP router as an independent service, migrate clients to a maintained WAMP library or a plain WebSocket or SSE transport, and decommission the bundle before upgrading PHP. For a Laravel application there is no migration path onto this bundle, only substitution with broadcasting, Reverb, Soketi, or a dedicated realtime service. Validate the target PHP runtime and framework version first, because those constraints usually decide the architecture.
Weaver
How can I help you explore Laravel packages today?