1. Build Realtime Applications
with
Laravel
Broadcasting

2. Mitul
Golakiya
About Me
8+ Years of Experience in Laravel
Open Source Lover
Laravel Consultant
Programmer & Speaker by Passion
CEO & Founder At InfyOm
Technologies

3. PHP Applications
• Website Development
• APIs Development
• E-Commerce Apps
• Static Websites

4. Realtime Applications
• The new Era of realtime applications
• No on want to refresh a page
• Socket.io
• Node.js takeover

5. Use
CasesLaravel Echo can be used in
various use cases where we
need updates from Backend
Server.
Real-time Chatting
App
Chatting
Backend Notifications
System
Notifications
Realtime Updates
from Backend
Realtime Updates
An app where we need
realtime collobrations
Realtime
Collobration

6. Socket.io

7. Socket.io
Socket.io is a event-driven library which enables
real-time and full duplex communication between
the Client and the Web servers by using
WebSocket protocol.
• Node.js server
• Javascript Client side Library for browser

8. REST vs Websockets

9. Laravel
Broadcasting

10. Laravel Broadcasting
• Possibility to send updates to frontend in
realtime
• Multiple connectors
• Socket.io with Echo Server with Redis
• Pusher
• Without leaving comfort of PHP & Laravel
• As simple as dispatching Laravel Events

11. How it Works?

12. Laravel with Pusher
Channel

13. Laravel Echo with Socket.io
Channel

14. Laravel Echo

15. Laravel Echo
Laravel Echo is a JavaScript library that makes it
painless to subscribe to channels and listen for
events broadcast by Laravel.
composer require pusher/pusher-php-server
"~4.0"
npm install –save laravel-echo pusher-js
composer require predis/predis
npm install –save socket.io-client

16. Channels &
Events

17. Channels
• Each application can have one channel or many,
and each client can choose which channels it
subscribes to.
• Channels provide a way of filtering data For
example, in a chat application there may be a
channel for people who want to discuss 'dogs’
• A way of controlling access to different streams of
information.
• Channels don't need to be explicitly created, and
areinstantiated on client demand.

18. Types of Channels
• Public channels can be subscribed to by anyone
who knows their name
• Private channels should have a private- prefix. They
introduce a mechanism which lets your server
control access to the data you are broadcasting
• Presence channels should have a presence- prefix
and are an extension of private channels. They let
you 'register' user information on subscription, and
let other members of the channel know who's
online.

19. Events
• Events are the primary method of packaging
messages in the Channels system. they form the
basis of all communication.
• They are essentially 'named messages' which means
you can set up 'handlers' in your client code to deal
with the various types.
• They are used for 'client-side' routing, and should
not be used as filters.
• Events can be seen as a notification of something
happening on your system, and they are often
named in the past tense.

20. Configuration

21. Configuration
• Config File - config/broadcasting.php
• Broadcast Drivers: Pusher + Redis + Log
• Add/Uncomment
AppProvidersBroadcastServiceProvider

22. Pusher Channels
composer require pusher/pusher-php-server "~4.0"
Update config/broadcasting.php file with credentials
resources/js/bootstrap.js
import Echo from "laravel-echo";
window.Pusher = require('pusher-js’);
window.Echo = new Echo({
broadcaster: 'pusher’,
key: 'your-pusher-channels-key’
});

23. Socket.io
composer require predis/predis
npm install --save socket.io-client
resources/js/bootstrap.js
import Echo from "laravel-echo";
window.Pusher = require('socket.io-client’);
window.Echo = new Echo({
broadcaster: 'socket.io’,
host: window.location.hostname + ':6001’
});
npm install -g laravel-echo-server

24. Demo Time

25. Thank You
Questions?
www.infyom.com mitul@infyom.com @mitulgolakiya infyomlabs