Weave Code
Remote Event Laravel Package
symfony/remote-event
Symfony RemoteEvent helps your app receive, validate, and handle remote events (like webhooks) in a consistent way. It provides tooling to parse payloads, verify signatures, map to event objects, and process them through Symfony’s event/HTTP workflows.
Eases handling remote events
Frequently asked questions about Remote Event
- Can Symfony RemoteEvent work with Laravel’s built-in webhook handling (e.g., Stripe, GitHub) without extra dependencies?
- Yes, RemoteEvent simplifies webhook integration by validating signatures, parsing payloads, and dispatching Laravel events automatically. For Stripe or GitHub, you’d only need `symfony/http-client` (included via Composer) and Laravel’s `Validator` facade for basic rules. Avoid over-engineering—start with HTTP transport and add queues later if needed.
- How do I map Symfony RemoteEvent objects to Laravel’s native Event class for dispatching?
- Create a wrapper class (e.g., `LaravelRemoteEvent`) that implements Symfony’s `RemoteEventInterface` and delegates to Laravel’s `Event` class. Use a service provider to bind Symfony’s `RemoteEventInterface` to your wrapper, then dispatch via `event(new YourLaravelEvent($remoteEvent->getData()))`. This bridges Symfony’s event system to Laravel’s.
- Does Symfony RemoteEvent support Laravel’s Horizon for queue-based event processing?
- Indirectly, yes. RemoteEvent uses Symfony’s `Messenger` component, which can integrate with Laravel’s queues if you wrap its transport layer. For Horizon, configure `symfony/messenger` to use Laravel’s queue connection (e.g., `doctrine://default`) and dispatch remote events as jobs. Start with HTTP transport first to avoid complexity.
- What Laravel versions are officially supported by Symfony RemoteEvent?
- Symfony RemoteEvent itself doesn’t enforce Laravel versioning, but it requires PHP 8.1+ and works best with Laravel 10+ for dependency injection and event system compatibility. Test thoroughly with Laravel 9 if needed, but expect minor adjustments for service container binding or event dispatching.
- How can I validate remote event payloads using Laravel’s validation rules instead of Symfony’s Validator?
- Symfony RemoteEvent supports both. For simple cases, use Laravel’s `Validator` facade by injecting it into your event handler and validating the deserialized payload manually. For complex schemas (e.g., JSON Schema), leverage Symfony’s `Validator` via a service provider and bind it to Laravel’s container. Hybrid approaches work well.
- Will Symfony RemoteEvent cause performance issues if remote events trigger synchronous Laravel logic?
- Yes, synchronous processing risks timeouts or blocking requests. Offload remote event handling to Laravel queues (Horizon) or async jobs. Use Symfony’s `Messenger` with a queue transport (e.g., `doctrine://default`) to decouple processing. Monitor queue backlogs and adjust worker counts in Horizon.
- Are there alternatives to Symfony RemoteEvent for Laravel webhooks that don’t require Symfony dependencies?
- Yes, consider `spatie/laravel-webhook-server` for simple webhooks or `fruitcake/laravel-webhooks` for signature validation. For event-driven architectures, `laravel-websockets` (Pusher) or `beyondcode/laravel-websockets` handle real-time events. Symfony RemoteEvent shines for cross-service events with validation/transport flexibility but adds dependency overhead.
- How do I test Symfony RemoteEvent in Laravel with mocked HTTP responses or failed signatures?
- Use Laravel’s `Http` facade or `Mockery` to mock Symfony’s `HttpClient`. For signature validation, inject a fake `RemoteEvent` with a tampered payload and assert exceptions. Test event dispatching with Laravel’s `Event` facade or `Pest` assertions. Example: `$this->fake()->events();` to verify events fire correctly.
- Can Symfony RemoteEvent handle AMQP/RabbitMQ for high-throughput event processing in Laravel?
- Not natively, but you can integrate it with Laravel via `pestle` or `php-amqplib`. Configure Symfony’s `Messenger` to use AMQP transport and bind it to Laravel’s service container. Start with HTTP transport to validate your use case before adding AMQP complexity, as it requires additional setup for connection pooling and error handling.
- How should I log or audit remote events processed by Symfony RemoteEvent in Laravel?
- Use Laravel’s `Log` facade to record event processing (e.g., `Log::info('Processed remote event', ['event' => $remoteEvent->getName()])`). For auditing, store metadata (e.g., payload hash, timestamp) in a database table or use Laravel’s `activitylog` package. Symfony’s `Monolog` can be bridged via a custom handler if deeper integration is needed.
Weaver
How can I help you explore Laravel packages today?