Slide 1

Slide 1 text

QUEUES & ASYNC APPS MACEIÓ DEV MEETUP#14

Slide 2

Slide 2 text

HI, I’M TONY.

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

QUEUES

Slide 6

Slide 6 text

QUEUES

Slide 7

Slide 7 text

PROBLEM

Slide 8

Slide 8 text

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

Slide 9

Slide 9 text

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

Slide 10

Slide 10 text

JUST KIDDING...

Slide 11

Slide 11 text

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!

Slide 12

Slide 12 text

CURRENT INFRASTRUCTURE

Slide 13

Slide 13 text

CREATE A SERVER

Slide 14

Slide 14 text

CREATE A SERVER

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

QUEUES TO THE RESCUE!

Slide 17

Slide 17 text

CREATE A SERVER

Slide 18

Slide 18 text

CREATE A SERVER W/ QUEUES

Slide 19

Slide 19 text

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

Slide 20

Slide 20 text

CURRENT INFRASTRUCTURE

Slide 21

Slide 21 text

CURRENT INFRASTRUCTURE

Slide 22

Slide 22 text

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?

Slide 23

Slide 23 text

CURRENT INFRASTRUCTURE

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

WEBSOCKETS

Slide 26

Slide 26 text

WEBSOCKETS

Slide 27

Slide 27 text

HTTP

Slide 28

Slide 28 text

No content

Slide 29

Slide 29 text

No content

Slide 30

Slide 30 text

CLIENT-SERVER

Slide 31

Slide 31 text

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

Slide 32

Slide 32 text

No content

Slide 33

Slide 33 text

WEBSOCKETS

Slide 34

Slide 34 text

WEBSOCKETS

Slide 35

Slide 35 text

No content

Slide 36

Slide 36 text

No content

Slide 37

Slide 37 text

TCP

Slide 38

Slide 38 text

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

Slide 39

Slide 39 text

WEBSOCKETS

Slide 40

Slide 40 text

WEBSOCKETS

Slide 41

Slide 41 text

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

Slide 42

Slide 42 text

WEBSOCKETS PROVIDERS

Slide 43

Slide 43 text

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

Slide 44

Slide 44 text

CURRENT INFRASTRUCTURE

Slide 45

Slide 45 text

CURRENT INFRASTRUCTURE

Slide 46

Slide 46 text

DEMO!

Slide 47

Slide 47 text

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