Building Real-Time Laravel Apps with Pusher

Bridge v Event Broadcasting

By using the bridge instead of Event Broadcasting you don't need to adhere to some of the Event Broadcasting rules and it provides consistency when it comes to accessing the Pusher instance for other pieces of Pusher functionality such as authenticating channel subscriptions, querying application state (e.g. channels that have active subscriptions) and validating incoming Pusher WebHooks.

However, by using event broadcasting you are completely decoupling your back-end functionality from having any reliance on Pusher's broadcast messaging which means you can quickly switch out the message broadcasting service that you're using.

Make the best choice for your app.

Which one will we use?

To keep things simple, we're going to be using the vikla/pusher Laravel Pusher Bridge for the rest of the workshop.

Where next?

Let's admit it, sometimes things just don't work. So, let's see how you can debug your Pusher server-side integration.