This presentation was made in the #14 Maceio DEV Meetup (https://www.meetup.com/pt-BR/maceio-dev-meetup/events/236962766/) After the slides, a demo was presented: https://github.com/tonysm/laravel-queue-async-apps-example References from the slides https://speakerdeck.com/igorw/websockets-confoo https://changelog.com/podcast/31 “The WebSocket Protocol” https://www.3pillarglobal.com/insights/rabbitmq-understanding-message-broker https://laravel.com/docs/5.4/broadcasting https://laravel.com/docs/5.4/queues http://kr.github.io/beanstalkd/ https://github.com/tonysm/laravel-queue-async-apps-example

1. QUEUES &
ASYNC APPS
MACEIÓ DEV MEETUP#14

2. HI, I’M TONY.

5. QUEUES

6. QUEUES

7. PROBLEM

8. LET’S SAY YOU’RE
SENDING AN EMAIL...

9. LET’S SAY YOU’RE
SENDING AN EMAIL...

10. JUST KIDDING...

11. SERVER PROVISIONING SERVICE
➔ CREATE A NEW SERVER
◆ SPIN UP A NEW SERVER INSTANCE
◆ WAIT FOR IT TO BOOT
◆ PROVISION THE SERVER (INSTALL BASE DEPENDENCIES - LIKE GIT, PHP...)
◆ NOTIFY THE USER THE SERVER IS READY (APP NOTIFICATION, SLACK…)
◆ DONE!

12. CURRENT INFRASTRUCTURE

13. CREATE A SERVER

14. CREATE A SERVER

16. QUEUES TO
THE RESCUE!

17. CREATE A SERVER

18. CREATE A SERVER W/ QUEUES

19. QUEUES
➔ BROKER (AKA. MESSAGE BROKER): SOME INTERMEDIARY TOOL USED TO
EASILY SEND MESSAGES BETWEEN TWO APPLICATIONS;
◆ REDIS, DATABASE, RABBITMQ, BEANSTALKD, FILESYSTEM...
➔ WORKER: SOME APPLICATION/PROCESS THAT ACTS AS A
“CONSUMER” FOR THE QUEUE MESSAGES/JOBS.
◆ CAN BE A DIFFERENT SERVER OR EVEN IN DIFFERENT LANGUAGES

20. CURRENT INFRASTRUCTURE

21. CURRENT INFRASTRUCTURE

22. MORE ABOUT QUEUES
➔ YOU CAN SPLIT YOUR JOBS INTO CHANNELS AND HAVE APPROPRIATE
WORKERS PROCESSING PER CHANNEL;
➔ CHOOSE A GOOD MESSAGE BROKER, LIKE AWS SQS FOR PRODUCTION;
➔ BE AWARE OF CONCURRENCY PROBLEMS BETWEEN WORKERS AND
RESOURCES;
➔ PREPARE FOR FAILURE: WHAT SHOULD HAPPEN?

23. CURRENT INFRASTRUCTURE

25. WEBSOCKETS

26. WEBSOCKETS

27. HTTP

30. CLIENT-SERVER

31. HTTP
FEATURES
➔ STATELESS;
➔ MEDIA INDEPENDENT;
➔ CACHING;
➔ AUTHENTICATION;
➔ HEADERS.

33. WEBSOCKETS

34. WEBSOCKETS

37. TCP

38. TCP
FEATURES
➔ CONNECTION-ORIENTED;
➔ DATA IS BROKEN IN
ENVELOPES/PACKETS TO BE
DELIVERED PIECE BY PIECE;
➔ PERSISTENT CONNECTION.

39. WEBSOCKETS

40. WEBSOCKETS

41. WEBSOCKETS
FEATURES
➔ APPLICATION LAYER
PROTOCOL (LIKE HTTP);
➔ USES TCP;
➔ BI-DIRECTIONAL,
FULL-DUPLEX
COMMUNICATION
BETWEEN WEB BROWSERS
AND WEB SERVERS.

42. WEBSOCKETS PROVIDERS

43. MORE ABOUT PUSHER...
➔ ACCESS CONTROL
➔ INTEGRATIONS
➔ CLIENT EVENTS
➔ FREE FOR <=200K
MESSAGES/DAY && <=100
SIMULTANEOUS CONNECTIONS

44. CURRENT INFRASTRUCTURE

45. CURRENT INFRASTRUCTURE

46. DEMO!

47. REFERENCES
❏ https://speakerdeck.com/igorw/websockets-confoo
❏ https://changelog.com/podcast/31 “The WebSocket Protocol”
❏ https://www.3pillarglobal.com/insights/rabbitmq-understanding-mes
sage-broker
❏ https://laravel.com/docs/5.4/broadcasting
❏ https://laravel.com/docs/5.4/queues
❏ http://kr.github.io/beanstalkd/
❏ https://github.com/tonysm/laravel-queue-async-apps-example