---
title: "Events"
canonical_url: "https://handbook.propay.co.za/laravel/events"
---
# Events

## Minimize the number of traits

By default, Laravel adds several traits to a new Event class, even if they are not needed in your particular case. It’s still better to control traits more explicitly.

<code-group>

```diff [PHP]
- use Dispatchable, InteractsWithSockets, SerializesModels;
+ use SerializesModels; // only if the Event will be used with Queued Event Listeners
```

</code-group>

Explanation:

- `Dispatchable` adds static methods to simplify event dispatching, like `YourEvent::dispatch()`. We do not use this syntax, so we don’t need this trait. Please use `\Illuminate\Support\Facades\Event` facade instead, e.g. `Event::dispatch(new YourEvent())`.
- `SerializesModels` gracefully serializes any Eloquent models when the event object contains Eloquent models and is going to be serialized using PHP's serialize function, such as when using queued listeners.
- `InteractsWithSockets` is for broadcasting only, e.g. when using Laravel Echo.

Best practices:

- Tailor Event class traits based on specific needs rather than using the default set.
- Understand the implications of each trait to avoid unnecessary overhead or missing functionality.
- Event class should be `final readonly`


## Sitemap

See the full [sitemap](https://handbook.propay.co.za/sitemap.md) for all pages.
