Slide 1

Slide 1 text

Websocket API Beer City Code 2019 Building a real time ⋆ ⋆ in Phoenix

Slide 2

Slide 2 text

@jwright

Slide 3

Slide 3 text

jamie @brilliantfantastic.com

Slide 4

Slide 4 text

@jwright http://speakerdeck.com/jwright

Slide 5

Slide 5 text

Background Some

Slide 6

Slide 6 text

Background Some

Slide 7

Slide 7 text

Background Some http://chronic.io

Slide 8

Slide 8 text

Background Some

Slide 9

Slide 9 text

Background Some

Slide 10

Slide 10 text

Background Some Server is gold copy Server pushes events to clients Clients displays event

Slide 11

Slide 11 text

Background Some Server triggers push smart notifications

Slide 12

Slide 12 text

Background Some Events at any second 

Slide 13

Slide 13 text

Background Some Demo

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

Websockets

Slide 16

Slide 16 text

Websocket What’s a

Slide 17

Slide 17 text

Websocket What’s a Protocol

Slide 18

Slide 18 text

Websocket Full-duplex connection Both sides can chat at same time

Slide 19

Slide 19 text

Http Simplex connection One side can chat at a time

Slide 20

Slide 20 text

Websocket What’s a https://tools.ietf.org/html/rfc6455 RFC

Slide 21

Slide 21 text

Websocket What’s a https://www.w3.org/TR/websockets/ W3C Spec

Slide 22

Slide 22 text

Websocket What’s a

Slide 23

Slide 23 text

Websocket What’s a Starts with a Handshakes via HTTP

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

No content

Slide 26

Slide 26 text

TCP (C’est une pipe) HTTP W ebSocket

Slide 27

Slide 27 text

Websockets Why we chose

Slide 28

Slide 28 text

Realtime Websockets Why we chose

Slide 29

Slide 29 text

Websockets Why we chose Eventful

Slide 30

Slide 30 text

Phoenix Why

Slide 31

Slide 31 text

Phoenix Why WebSockets

Slide 32

Slide 32 text

Phoenix Why Elixir

Slide 33

Slide 33 text

Phoenix Why Stateful

Slide 34

Slide 34 text

Fast Phoenix Why

Slide 35

Slide 35 text

Example APIs

Slide 36

Slide 36 text

Example APIs https://api.slack.com/rtm Send messages in channel Receive team events Receive user presence

Slide 37

Slide 37 text

Example APIs https://pusher.com/docs/pusher_protocol Receive system events Receive user presence Trigger client events

Slide 38

Slide 38 text

Example APIs https://getstream.io/docs/#realtime Receive feed changes

Slide 39

Slide 39 text

Works How it

Slide 40

Slide 40 text

Connecting

Slide 41

Slide 41 text

Connecting

Slide 42

Slide 42 text

Connecting

Slide 43

Slide 43 text

Connecting Give clients a starting point Identify events from a single endpoint (client) Opportunity to authenticate

Slide 44

Slide 44 text

No content

Slide 45

Slide 45 text

Connecting

Slide 46

Slide 46 text

Connecting

Slide 47

Slide 47 text

Connecting

Slide 48

Slide 48 text

Channels Joining

Slide 49

Slide 49 text

Channels Joining Custom Protocol

Slide 50

Slide 50 text

Channels Joining Multiplexed

Slide 51

Slide 51 text

Channels Joining PubSub

Slide 52

Slide 52 text

Channels Joining Built In

Slide 53

Slide 53 text

Channels Joining

Slide 54

Slide 54 text

Channels Joining

Slide 55

Slide 55 text

Channels Joining

Slide 56

Slide 56 text

Channels The Problem with

Slide 57

Slide 57 text

Problems { topic: “events:1234”, event: “phx_join” } { topic: “events:1234”, event: “phx_reply”, payload: { ok: true, token: “1234” }}} WS WS WS WS Joining Channels

Slide 58

Slide 58 text

Problems Joining Channels Remove complicated setup from clients Build reconnection/ heartbeat logic https://bit.ly/2WjtKxZ

Slide 59

Slide 59 text

Messages

Slide 60

Slide 60 text

Messages Meat

Slide 61

Slide 61 text

Messages Event name Event data

Slide 62

Slide 62 text

Messages Incoming

Slide 63

Slide 63 text

Messages Incoming

Slide 64

Slide 64 text

Messages Incoming

Slide 65

Slide 65 text

Messages Incoming

Slide 66

Slide 66 text

Messages Incoming

Slide 67

Slide 67 text

Messages Outgoing

Slide 68

Slide 68 text

Messages Outgoing

Slide 69

Slide 69 text

Messages Outgoing

Slide 70

Slide 70 text

Outgoing

Slide 71

Slide 71 text

No content

Slide 72

Slide 72 text

Review

Slide 73

Slide 73 text

Review POST /graphql { url: “ws://…”, token: “1234” } HTTP HTTP HTTP HTTP Connecting { mutation: { connect: { … } }

Slide 74

Slide 74 text

Review [“timers:start”, { duration: 1500, timestamp: 1273485 } ] [“timers:started”, { id: 1234, duration: 1500, remaining_time: 1500, status: “running” } ] WS WS WS WS Sending Messages

Slide 75

Slide 75 text

Thank You!

Slide 76

Slide 76 text

Questions?

Slide 77

Slide 77 text

@jwright