1
00:00:01,680 --> 00:00:05,320
Hello and welcome to this week's
episode of Edge Talk. 

2
00:00:05,960 --> 00:00:08,680
This week this is maybe the 
first in a few months, but we're

3
00:00:08,680 --> 00:00:11,960
back. 
So today we're going to focus on

4
00:00:12,840 --> 00:00:18,240
real time, everything real time 
and how we can make the user 

5
00:00:18,240 --> 00:00:23,520
experience better and how we can
optimize. 

6
00:00:24,440 --> 00:00:26,320
Or enhance. 
Enhance. 

7
00:00:27,320 --> 00:00:30,240
And make totally new use cases 
that previously weren't. 

8
00:00:30,320 --> 00:00:33,600
Yeah, possible. 
And you can actually think about

9
00:00:33,600 --> 00:00:37,240
it as bringing like making it 
more modern. 

10
00:00:37,320 --> 00:00:38,400
Right. 
Yeah. 

11
00:00:38,400 --> 00:00:40,960
All right. 
OK, I guess maybe we should stop

12
00:00:40,960 --> 00:00:42,600
here because my explanation is 
not. 

13
00:00:43,040 --> 00:00:46,760
The thing is, I think that we've
sort of like kept everyone, 

14
00:00:46,880 --> 00:00:48,480
everyone on the cliffhanger 
here. 

15
00:00:48,480 --> 00:00:50,160
So what are we actually going to
talk about? 

16
00:00:50,160 --> 00:00:57,640
OK, I'm not talking about web 
socket and fan out. 

17
00:00:57,920 --> 00:01:00,840
Yes. 
Woo Hoo, I got it right. 

18
00:01:01,320 --> 00:01:04,959
And so that was a long talk 
around what we're actually going

19
00:01:04,959 --> 00:01:07,160
to discuss. 
So what is it? 

20
00:01:07,200 --> 00:01:09,880
Yes. 
I think we could start with web 

21
00:01:09,880 --> 00:01:14,280
sockets because that's the 
generic technology and I think 

22
00:01:14,280 --> 00:01:19,400
that that's a good leeway into 
what it is and then sort of jump

23
00:01:19,400 --> 00:01:24,160
into what is fan out. 
Yeah, I think slash pushpin, 

24
00:01:24,160 --> 00:01:27,320
which is also a word. 
So there's going to be some, 

25
00:01:28,200 --> 00:01:35,480
some new names or lingo, maybe, 
umm, but in a way it's, it's 

26
00:01:35,480 --> 00:01:39,600
still going to be technical 
topics and web technology, 

27
00:01:39,600 --> 00:01:43,000
etcetera. 
But if you Google what is 

28
00:01:43,000 --> 00:01:47,640
Websockets, the Google AI 
summary will tell you that the 

29
00:01:47,720 --> 00:01:51,640
the biggest difference is that a
normal HTTP connection is like 

30
00:01:52,160 --> 00:01:55,480
sending a letter, whereas 
Websocket is a phone call. 

31
00:01:56,640 --> 00:02:03,200
That's the most generic term, 
which means that even though 

32
00:02:03,200 --> 00:02:07,640
there is some parts of a delay 
in a phone call, it's still 

33
00:02:07,640 --> 00:02:09,960
going to be real time because 
you're still going to have an 

34
00:02:09,960 --> 00:02:11,840
open communication back and 
forth. 

35
00:02:12,280 --> 00:02:15,440
And the connection is going to 
stay open for as long as the 

36
00:02:15,440 --> 00:02:20,520
call is going on, whereas the 
the mail analogy is very 

37
00:02:20,520 --> 00:02:22,040
different. 
Yeah, yeah. 

38
00:02:23,240 --> 00:02:27,720
So that opens up for some 
interesting use cases online. 

39
00:02:30,480 --> 00:02:34,360
One is and I think the lowest 
hanging fruit that people talk 

40
00:02:35,000 --> 00:02:40,160
sort of, OK, direct 
communication, open connection. 

41
00:02:40,160 --> 00:02:44,360
OK, let's make a shaft program. 
That's probably the the lowest 

42
00:02:44,360 --> 00:02:47,640
hanging fruit in terms of what 
do I use web sockets for? 

43
00:02:49,320 --> 00:02:54,640
Yeah, and I would. 
Say that it's sort of like the 

44
00:02:54,720 --> 00:02:58,720
one of the one of the easiest 
one is also that, Hey, if I can,

45
00:03:00,520 --> 00:03:04,920
if I make make updates 
previously, you know, on a on a 

46
00:03:04,920 --> 00:03:09,120
web page or or Jason object or 
whatever it might be, we sort of

47
00:03:09,120 --> 00:03:14,000
like had to either do have 
service server polling where 

48
00:03:14,000 --> 00:03:17,440
sort of like your JavaScript 
would Hey, like, hey, anything 

49
00:03:17,440 --> 00:03:23,320
new, anything new, anything new.
Or you could actually have long 

50
00:03:23,320 --> 00:03:25,800
lived connections, which was 
like server side. 

51
00:03:26,160 --> 00:03:30,400
So, but it was over an HTTP 
connect HTTP connection that 

52
00:03:30,400 --> 00:03:35,320
just didn't close. 
So it was ugly hack of HTTP, but

53
00:03:35,320 --> 00:03:37,360
then sort of like web sockets 
came along. 

54
00:03:37,360 --> 00:03:41,880
And so like that, it was sort of
like built for staying connected

55
00:03:42,080 --> 00:03:44,920
for a long time. 
Is this a new? 

56
00:03:44,960 --> 00:03:46,400
Technology. 
Web sockets? 

57
00:03:46,760 --> 00:03:51,240
Yeah, not really, no, but but at
the same time, the all other 

58
00:03:51,360 --> 00:03:55,080
ugly hacks were prior to that 
and were there because of a 

59
00:03:55,080 --> 00:03:57,760
reason, because web sockets 
weren't weren't around. 

60
00:03:58,600 --> 00:04:02,880
And I think isn't web sockets 
like maybe an ugly duckling of 

61
00:04:02,880 --> 00:04:05,880
web technology In many cases I 
think as well. 

62
00:04:07,200 --> 00:04:09,880
We all. 
Hack on a hack on a hack. 

63
00:04:10,280 --> 00:04:13,160
Yeah, yeah. 
And I also think that why why 

64
00:04:13,160 --> 00:04:16,120
use web sockets? 
Why if I have an application 

65
00:04:16,120 --> 00:04:19,920
that that needs an open 
connection yadda yadda, would it

66
00:04:19,920 --> 00:04:23,120
be web-based? 
Is that the most optimal news 

67
00:04:23,120 --> 00:04:28,960
Case 151010 to 15 years ago, we 
would probably be in a native 

68
00:04:28,960 --> 00:04:34,000
application that you run on on 
your desktop, where as a client 

69
00:04:34,000 --> 00:04:38,760
server set up using a random 
port requiring you to open up 

70
00:04:38,760 --> 00:04:44,120
your router, the firewall and 
and like a different type of 

71
00:04:46,120 --> 00:04:54,000
deployment and maintenance of 
that type of like the end goal 

72
00:04:54,000 --> 00:04:57,960
would still be a messaging or 
something real time. 

73
00:04:58,480 --> 00:05:04,240
Yeah, on the long connection. 
So it's it's still trying to 

74
00:05:04,240 --> 00:05:07,440
solve the same thing that we 
always try to solve in IT, but I

75
00:05:07,440 --> 00:05:11,720
think it's using websockets in 
in a way where you want to have 

76
00:05:11,720 --> 00:05:15,640
some sort of client server or 
clients to server. 

77
00:05:17,680 --> 00:05:20,760
Connection that is, yeah, that 
stays up instead of, you know, 

78
00:05:20,760 --> 00:05:25,640
the, you know, being just a sort
of like a get, get response type

79
00:05:25,960 --> 00:05:27,440
scenario. 
Yeah, for sure. 

80
00:05:28,160 --> 00:05:30,560
So what will this? 
What would be the impact then? 

81
00:05:30,640 --> 00:05:32,560
Like when you do this instead of
the old way. 

82
00:05:34,040 --> 00:05:38,840
One of the impacts is that it's 
you saying the the web 

83
00:05:39,120 --> 00:05:44,440
protocols, it's you saying all 
the things in and around serving

84
00:05:44,440 --> 00:05:50,200
and getting web documents. 
So existing open ports in a 

85
00:05:50,200 --> 00:05:53,960
firewall WAFF inspection is 
there. 

86
00:05:54,880 --> 00:05:59,600
Browser support is widespread, 
so you don't need specific 

87
00:05:59,600 --> 00:06:03,280
applications and you don't have 
to do firewall configuration and

88
00:06:03,280 --> 00:06:06,240
and a lot of that stuff. 
So it's it. 

89
00:06:06,880 --> 00:06:12,280
Or to figure out weird protocols
that sort of like as as you 

90
00:06:12,280 --> 00:06:15,880
spoke about sort of like you 
don't need to one, one can 

91
00:06:15,880 --> 00:06:20,040
definitely remember the days of 
Spotify's peer-to-peer 

92
00:06:20,040 --> 00:06:25,000
distribution of, of audio. 
Yeah, which obviously it never 

93
00:06:25,000 --> 00:06:28,280
worked at my previous employer 
because they were very strict on

94
00:06:28,280 --> 00:06:32,360
what what the firewall allowed 
and this didn't allow through. 

95
00:06:33,760 --> 00:06:38,960
So using this web standards 
makes everything much more, you 

96
00:06:38,960 --> 00:06:44,440
know, frictionless I would say. 
And I think that is the argument

97
00:06:44,440 --> 00:06:49,680
on why using standards in 
general is. 

98
00:06:50,800 --> 00:06:53,840
Recommended. 
Is there a benefit for like the 

99
00:06:53,840 --> 00:06:56,440
user experience? 
So I mentioned, I mentioned the 

100
00:06:56,440 --> 00:06:59,360
sort of like you have the server
polling, which is sort of like 

101
00:06:59,360 --> 00:07:03,720
at a normally or a set interval 
you fetch something or you have 

102
00:07:03,720 --> 00:07:07,960
the long lived connections which
obviously or service, service 

103
00:07:08,120 --> 00:07:13,000
side sent events. 
But you never had any control 

104
00:07:13,000 --> 00:07:17,440
over if how long that you know 
if you had the polling you would

105
00:07:17,440 --> 00:07:20,960
say every 30 seconds. 
You know that's 30 seconds can 

106
00:07:20,960 --> 00:07:24,800
be pretty off off real time with
the long lived connections. 

107
00:07:24,920 --> 00:07:29,080
You know, when the service 
sending stuff over normal HTTP, 

108
00:07:29,080 --> 00:07:31,400
you couldn't guarantee that it 
would stay up. 

109
00:07:32,240 --> 00:07:35,720
So just going into websockets 
sort of like allows you to do a 

110
00:07:35,720 --> 00:07:38,080
much, much more robust 
infrastructure thing. 

111
00:07:38,480 --> 00:07:42,880
Sort of like the browser will 
support reconnecting if if it 

112
00:07:42,880 --> 00:07:46,400
loses the connection. 
So you don't need to again, it's

113
00:07:46,400 --> 00:07:48,840
frictionless. 
I don't need to invent all the 

114
00:07:48,840 --> 00:07:53,280
plumbing and all the 
redundancies that I want for for

115
00:07:53,280 --> 00:07:56,240
a protocol that I would invent 
myself, not that I would, but 

116
00:07:56,400 --> 00:07:58,120
sort of like if you ever thought
about it. 

117
00:07:59,520 --> 00:08:00,840
You have thought about it, 
haven't you? 

118
00:08:01,680 --> 00:08:02,840
No. 
I think. 

119
00:08:03,280 --> 00:08:05,480
Well, maybe. 
Maybe. 

120
00:08:07,320 --> 00:08:13,040
But you can still play around 
with how like how the data like 

121
00:08:13,040 --> 00:08:19,320
the, the data model in where you
send the, the data in the web 

122
00:08:19,320 --> 00:08:22,560
sockets, like the communication 
and and the paid outs that that 

123
00:08:22,560 --> 00:08:25,040
could be whatever you define it 
to be. 

124
00:08:28,400 --> 00:08:32,640
So I, I think that I think that 
websockets and that type of 

125
00:08:32,640 --> 00:08:38,880
technology opens up another or 
an additional way to, to develop

126
00:08:38,880 --> 00:08:43,840
the experience online. 
And I think if you, if you tried

127
00:08:43,840 --> 00:08:50,160
to book like concert tickets 15 
years ago, like the server 

128
00:08:50,160 --> 00:08:53,440
crashed and then you just had to
refresh until they fixed the 

129
00:08:53,440 --> 00:08:56,440
server and you got a slot. 
Otherwise you had to wait until 

130
00:08:56,440 --> 00:08:59,480
the server crashed again. 
And then it was just a matter of

131
00:09:00,680 --> 00:09:05,000
a lot of luck being out early 
and be fast on refresh. 

132
00:09:06,040 --> 00:09:07,680
Whereas today a lot. 
Done. 

133
00:09:07,680 --> 00:09:11,280
That's right. 
Yes, no, I'm Swedish. 

134
00:09:11,280 --> 00:09:20,240
I took my turn no and I but 
today you can use websockets as 

135
00:09:20,240 --> 00:09:24,800
an example and and that then 
it's easy to do a stateful 

136
00:09:24,800 --> 00:09:26,600
queue. 
So then it is good for the user 

137
00:09:26,600 --> 00:09:27,920
experience, yeah. 
Yeah, yeah. 

138
00:09:28,160 --> 00:09:33,600
So that's that's one of the 
users is the face you could do 

139
00:09:34,400 --> 00:09:37,480
messaging. 
How many of us haven't been to a

140
00:09:37,480 --> 00:09:43,320
website where the pop up in the 
bottom right corner saying is 

141
00:09:43,320 --> 00:09:44,840
there anything I can help you 
with? 

142
00:09:45,680 --> 00:09:48,360
Every single site today, right? 
Yeah, yeah. 

143
00:09:49,360 --> 00:09:53,320
Many of that those features is a
web socket. 

144
00:09:53,320 --> 00:09:56,480
Even though it's an AEI bot in 
many cases, but it's still 

145
00:09:56,480 --> 00:10:00,680
between your browser and the 
website. 

146
00:10:00,680 --> 00:10:03,000
It's a it's usually a web 
socket. 

147
00:10:03,960 --> 00:10:07,120
Cool. 
So should we talked about web 

148
00:10:07,120 --> 00:10:09,080
sockets now? 
Should we talk about fan out? 

149
00:10:09,080 --> 00:10:10,880
Yes. 
Should we say that there's an 

150
00:10:10,880 --> 00:10:18,360
open source project called 
Pushpin which is free for anyone

151
00:10:18,360 --> 00:10:25,880
to use, but fastly calls are 
fork is maybe? 

152
00:10:25,880 --> 00:10:28,600
Not the correct. 
Yeah. 

153
00:10:28,760 --> 00:10:33,680
So, yeah. 
So it Fastly uses Pushpin, but 

154
00:10:33,680 --> 00:10:37,600
we call the product fan out in 
Fastly and it runs on every 

155
00:10:37,600 --> 00:10:40,200
server node in in the Fastly 
infrastructure. 

156
00:10:40,200 --> 00:10:43,200
Or is it pushpin as a service? 
Maybe could be? 

157
00:10:44,320 --> 00:10:48,760
It could be so, but it's it's. 
Are we creating new words here 

158
00:10:48,760 --> 00:10:51,880
or no? 
Yes, no, everything can be as a 

159
00:10:51,880 --> 00:10:53,440
service. 
Yeah. 

160
00:10:53,840 --> 00:10:55,840
We're going to start with 
marketing. 

161
00:10:55,840 --> 00:10:56,960
That's going to be my new job, 
yeah. 

162
00:10:58,000 --> 00:11:02,840
You can tell here. 
Playing with words? 

163
00:11:03,520 --> 00:11:05,320
No. 
But what's the difference time 

164
00:11:05,320 --> 00:11:10,040
markets between a fan out or 
pushpin compared to a web 

165
00:11:10,040 --> 00:11:10,680
socket? 
Oh. 

166
00:11:11,200 --> 00:11:14,160
Actually, yeah, Lisa is seems 
keen on answering, so yeah. 

167
00:11:14,680 --> 00:11:16,800
I I think I know the different 
difference. 

168
00:11:16,800 --> 00:11:19,320
Let's see if I I got the right 
answer. 

169
00:11:19,560 --> 00:11:22,120
Can we please delete this answer
if it's wrong? 

170
00:11:22,880 --> 00:11:25,040
Nope. 
No, we're doing live. 

171
00:11:25,120 --> 00:11:27,920
This is live messaging, so we 
can't really do that. 

172
00:11:29,280 --> 00:11:34,200
OK, so the difference is between
between web socket and fan out 

173
00:11:34,200 --> 00:11:37,240
is so that other people can join
the call. 

174
00:11:37,240 --> 00:11:41,680
OK, So yes, you're correct, 
absolutely correct. 

175
00:11:41,680 --> 00:11:44,280
I think that Mister was after 
what difference is between 

176
00:11:44,280 --> 00:11:48,880
pushpin and and fan out. 
But but that's that's a 

177
00:11:48,880 --> 00:11:51,760
definitely different question. 
But I think that you came came 

178
00:11:51,760 --> 00:11:55,880
to your, your answer is actually
better to start off with is that

179
00:11:56,320 --> 00:11:59,920
if we talk about web sockets, 
it's a one to one connection, 

180
00:11:59,920 --> 00:12:02,040
right? 
So it is between your browser 

181
00:12:02,040 --> 00:12:06,680
and the server application in 
fan out, it basically allows you

182
00:12:06,680 --> 00:12:11,120
to for a client to subscribe to 
a channel. 

183
00:12:11,800 --> 00:12:15,880
So all of a sudden you can have 
multiple clients on one channel,

184
00:12:15,920 --> 00:12:18,400
which means that there is one to
many. 

185
00:12:18,400 --> 00:12:22,120
Yeah, and but also multiple, 
like one client to multiple 

186
00:12:22,120 --> 00:12:24,720
channels. 
Yeah, yeah. 

187
00:12:24,760 --> 00:12:27,880
So you are correct, Lisa, that 
it's sort of like if you want 

188
00:12:27,880 --> 00:12:30,200
any. 
Question on an answer but. 

189
00:12:30,440 --> 00:12:33,080
But but a very good answer for 
sure. 

190
00:12:33,240 --> 00:12:37,320
Absolutely. 
That's good. 

191
00:12:39,040 --> 00:12:40,480
Teachers. 
That's how we get points, 

192
00:12:40,560 --> 00:12:43,000
anyhow. 
Yeah, yeah, yeah, exactly. 

193
00:12:44,960 --> 00:12:46,360
But. 
That matters. 

194
00:12:47,000 --> 00:12:49,400
Exactly. 
No, but I think that that's the 

195
00:12:49,400 --> 00:12:52,400
that's the sort of like the main
thing is that it is sort of like

196
00:12:52,440 --> 00:12:56,560
you, you can subscribe to 
different channels that can give

197
00:12:56,560 --> 00:12:58,200
you different types of 
information. 

198
00:12:58,240 --> 00:13:04,400
It is A1 to many type scenario. 
So if one send one client sends 

199
00:13:04,400 --> 00:13:08,360
a message, it's going to be sort
of like distributed to all the 

200
00:13:08,360 --> 00:13:11,640
clients that are listening to 
that Channel. 

201
00:13:12,240 --> 00:13:15,280
Does this sound familiar and 
have another name in the world? 

202
00:13:15,280 --> 00:13:19,200
Names. 
It's peer-to-peer, could be a 

203
00:13:19,200 --> 00:13:20,720
word. 
Pub sub. 

204
00:13:22,000 --> 00:13:29,320
Pub sum, Yeah, yeah, I think I 
spaced out. 

205
00:13:29,320 --> 00:13:33,000
That was yeah, pub sum. 
But yeah, so, so it is basically

206
00:13:33,000 --> 00:13:37,360
a pub publish subscribe 
scenario, but built on websocket

207
00:13:37,360 --> 00:13:40,680
technologies instead of other 
kinds of tech. 

208
00:13:41,160 --> 00:13:46,280
But it sort of like achieves the
same thing, which makes up why I

209
00:13:46,280 --> 00:13:51,080
would say that for for the most 
interesting scenarios, because 

210
00:13:51,080 --> 00:13:54,960
all of a sudden you can do a lot
of cool stuff with, you know, 

211
00:13:54,960 --> 00:13:59,080
multiple clients connected to 
the same channel listening to 

212
00:13:59,080 --> 00:14:00,880
and getting said the same 
messages, right? 

213
00:14:01,600 --> 00:14:04,720
Like multiplayer? 
Multiplayer is the definitely 

214
00:14:04,720 --> 00:14:06,280
the first one that comes to 
mind. 

215
00:14:06,640 --> 00:14:10,560
I know I would say that Web 
chats, yeah, definitely. 

216
00:14:11,480 --> 00:14:17,480
Yeah, it's opens up for 
authoritative messaging, which 

217
00:14:17,520 --> 00:14:20,760
means that you can have a 
centrally controlled 

218
00:14:20,760 --> 00:14:24,680
communication. 
So in a chat, for instance, or 

219
00:14:24,680 --> 00:14:29,280
even in even in a multiplayer 
game, all messages have to go 

220
00:14:29,280 --> 00:14:34,040
through an authoritative 
controller, which would be a fan

221
00:14:34,040 --> 00:14:37,920
out server, in in in in a faster
case, or out your own pushpin, 

222
00:14:40,360 --> 00:14:44,640
which means that you have the 
control of what's being sent to 

223
00:14:44,640 --> 00:14:48,480
all of the other users and it's 
real time. 

224
00:14:49,880 --> 00:14:54,400
Could this be something that can
be used for like different kinds

225
00:14:54,400 --> 00:14:58,720
of AI tools so you can keep that
kind of connection open or no? 

226
00:14:58,720 --> 00:15:05,120
Like it wouldn't be impossible, 
but I think isn't isn't the the 

227
00:15:05,120 --> 00:15:09,960
way many of these agents 
communicate on the MCP protocol.

228
00:15:09,960 --> 00:15:15,560
It's more, it's more of our push
and get. 

229
00:15:16,240 --> 00:15:17,960
Yeah. 
And and I think I would say that

230
00:15:17,960 --> 00:15:23,400
it's more of a one to one 
scenario anyway, but but I think

231
00:15:23,400 --> 00:15:26,600
that, you know, the number of 
use cases that that can be done 

232
00:15:26,600 --> 00:15:31,320
in A1 to many is pretty, you 
know, we we probably haven't 

233
00:15:31,320 --> 00:15:35,480
even explored the OR getting go 
gotten close to the number of 

234
00:15:35,760 --> 00:15:40,760
use cases that are, you know, 
possible or available to to use.

235
00:15:41,320 --> 00:15:43,600
You know I am. 
I hearing a competition here 

236
00:15:43,600 --> 00:15:46,680
with new use cases. 
Well, we'll see. 

237
00:15:47,000 --> 00:15:50,040
But it's sort of like the, the, 
the multiplayer gaming, sort of 

238
00:15:50,040 --> 00:15:53,080
like the social aspect of that, 
you know, having people in the 

239
00:15:53,080 --> 00:15:55,160
game being able to communicate 
with each other. 

240
00:15:55,440 --> 00:15:57,880
Or if you're in multiple games, 
you could, you know, have 

241
00:15:57,880 --> 00:16:02,880
different communications. 
But just in like, you know, news

242
00:16:03,960 --> 00:16:07,480
where you have the scenario 
where you have breaking news 

243
00:16:07,480 --> 00:16:11,360
kind of a thing. 
So you put all, every browser 

244
00:16:11,360 --> 00:16:15,000
that is on your website connects
to the breaking news channel. 

245
00:16:15,560 --> 00:16:19,200
So when when you actually have 
breaking news, you plat blast 

246
00:16:19,200 --> 00:16:23,360
that out onto that Channel and 
you get automatic distribution 

247
00:16:23,360 --> 00:16:27,120
to all of them instead of having
like let's say you have 

248
00:16:27,120 --> 00:16:31,560
1,000,000 readers, you need to 
manage 1,000,000 connections to 

249
00:16:31,560 --> 00:16:34,680
your application. 
You know, even if connections 

250
00:16:34,680 --> 00:16:37,360
are cheap, it adds up. 
Yeah, and it's also an 

251
00:16:37,360 --> 00:16:41,960
alternative if you have your 
like native app on Android and 

252
00:16:41,960 --> 00:16:46,160
and and iOS. 
It is an alternative into using 

253
00:16:46,160 --> 00:16:51,720
the notifications systems from 
the from the manufacturers. 

254
00:16:51,720 --> 00:16:56,080
If if you have an app with 
background activities it could 

255
00:16:56,080 --> 00:17:00,880
open a a web socket connection 
or using fan out to subscribe to

256
00:17:00,880 --> 00:17:05,800
topic and then you could push 
your own messaging to the app. 

257
00:17:06,440 --> 00:17:09,640
And then locally it actually 
generates the notification just 

258
00:17:09,640 --> 00:17:12,440
on your phone. 
So you don't have to use the the

259
00:17:12,440 --> 00:17:17,560
the main provided 1. 
Not sure if you can like TCO 

260
00:17:17,560 --> 00:17:21,480
wise if it's worth doing, but 
there are alternatives. 

261
00:17:22,240 --> 00:17:24,119
Yeah, I know. 
But at the same time, you know, 

262
00:17:24,119 --> 00:17:26,800
there might be fall back 
scenarios which you want to use,

263
00:17:26,800 --> 00:17:29,520
use it for or whatever. 
So I, I don't, you know, it 

264
00:17:29,680 --> 00:17:34,000
necessarily doesn't take away 
one use case for for another one

265
00:17:34,000 --> 00:17:37,240
or you know, one, one way of 
communicating with a client. 

266
00:17:37,600 --> 00:17:40,920
And obviously if you have, if 
you have an iOS app, you might 

267
00:17:40,920 --> 00:17:43,960
have a website as well where you
want to have the same kind of 

268
00:17:43,960 --> 00:17:48,280
features, but you can't 
obviously use a back, you know, 

269
00:17:48,320 --> 00:17:52,720
notification library that is for
iOS on web. 

270
00:17:53,520 --> 00:17:56,800
So then you'd probably need a 
web socket, you know, So, So 

271
00:17:56,800 --> 00:18:00,640
what you can do is get a more 
sort of like cohesive experience

272
00:18:00,640 --> 00:18:03,640
for the user. 
So even if you can do something 

273
00:18:03,640 --> 00:18:06,880
natively, you probably need an 
alternative as well. 

274
00:18:06,880 --> 00:18:09,600
When you're non-native, your 
client is non-native for some 

275
00:18:09,600 --> 00:18:10,640
reason. 
Yeah. 

276
00:18:12,600 --> 00:18:17,040
And I think we could mention 
every MQTT use case you could 

277
00:18:17,040 --> 00:18:23,360
think of, which is basically 
everything Internet of Things, 

278
00:18:25,680 --> 00:18:31,440
which is, which is an 
interesting spectrum of use 

279
00:18:31,440 --> 00:18:34,200
cases. 
So I don't, I don't this isn't 

280
00:18:34,200 --> 00:18:39,880
an IoT podcast, of course, but 
there's, I think that that's a 

281
00:18:39,920 --> 00:18:44,400
that's, that's a big use case. 
I know we spoke with one car 

282
00:18:44,400 --> 00:18:49,760
manufacturer that had a problem 
with the current IoT solution 

283
00:18:49,760 --> 00:18:54,560
lasting 30 plus messages from 
the car every time the door 

284
00:18:54,560 --> 00:18:57,440
opens because of a bug in the 
sensor. 

285
00:18:57,840 --> 00:19:01,520
So the sensor triggered too many
times and there was no way to 

286
00:19:01,880 --> 00:19:05,840
sort of scale down and filter 
the messages and it it just went

287
00:19:05,840 --> 00:19:10,480
straight into purpose built 
platform where they got charged 

288
00:19:10,480 --> 00:19:13,400
per message. 
Yeah. 

289
00:19:14,800 --> 00:19:18,840
That's. 
So putting just by putting 

290
00:19:19,000 --> 00:19:22,520
something like Fastly or fan 
outdoor push pit in front of us,

291
00:19:22,520 --> 00:19:26,800
such a solution would give you 
the ability to actually start to

292
00:19:27,720 --> 00:19:32,080
modify the messaging and to add 
logic into the messages. 

293
00:19:32,080 --> 00:19:35,600
So why would I run FANA? 
Why wouldn't I just install 

294
00:19:35,600 --> 00:19:42,040
Pushpin on a small server in 
small Bart or in Ireland? 

295
00:19:43,480 --> 00:19:47,360
Well, I think it boils down to 
the same thing we keep on saying

296
00:19:47,360 --> 00:19:49,280
each time. 
It's like performance. 

297
00:19:49,280 --> 00:19:53,520
Of course. 
Yeah, you know, Still, you know,

298
00:19:53,520 --> 00:19:57,000
we, we, you know what we, we 
still need something that is 

299
00:19:57,000 --> 00:20:00,240
faster than light. 
And then obviously then we can 

300
00:20:00,240 --> 00:20:03,360
retire and sort of like say 
that, hey, it's CDN and 

301
00:20:03,360 --> 00:20:07,600
distributed computing thing. 
Not, not required. 

302
00:20:07,600 --> 00:20:11,600
But, you know, we so far, I 
haven't heard any rumblings in 

303
00:20:11,600 --> 00:20:13,360
the Nobel Prize committee about 
that. 

304
00:20:14,000 --> 00:20:18,440
Now there's that they haven't 
gotten the formal submission 

305
00:20:18,440 --> 00:20:21,680
yet. 
No, so, so that is, you know, 

306
00:20:21,680 --> 00:20:26,160
it's if we talk about sort of 
like if we lump together push 

307
00:20:26,160 --> 00:20:32,320
pin and and fan out, the idea is
basically to have not have a 

308
00:20:32,320 --> 00:20:36,720
central server that receives and
sends all the messages. 

309
00:20:36,720 --> 00:20:39,480
It's sort of like push pin 
allows you obviously to, you 

310
00:20:39,480 --> 00:20:42,880
know, have multiple instances in
different locations. 

311
00:20:44,040 --> 00:20:46,320
I but you would still need to do
the routing. 

312
00:20:46,960 --> 00:20:50,400
But with the fan out, obviously 
you get the the distribution of 

313
00:20:50,400 --> 00:20:56,200
the Fastly network and our 
traffic routing to the closest 

314
00:20:56,200 --> 00:20:58,080
pub for the user etcetera, 
etcetera. 

315
00:20:58,920 --> 00:21:03,240
So you know, we, you could 
probably solve it with a pub sub

316
00:21:03,240 --> 00:21:07,360
kind of a scenario where the 
with the server in Ireland, your

317
00:21:07,360 --> 00:21:11,200
US users would be sad, your 
Asian users would be sad. 

318
00:21:11,200 --> 00:21:14,960
And but if you sort of like 
distribute the handling of the 

319
00:21:14,960 --> 00:21:17,840
messages, then obviously you get
better performance. 

320
00:21:18,200 --> 00:21:21,800
And you know, we LED with saying
that, hey, this is about real 

321
00:21:21,800 --> 00:21:24,120
time. 
So then obviously performance is

322
00:21:25,160 --> 00:21:27,600
utmost important. 
Yeah, yeah. 

323
00:21:27,840 --> 00:21:30,960
So I would say that yeah, it's, 
it's it's easy. 

324
00:21:30,960 --> 00:21:33,920
It's always performance. 
So it's like why adding web 

325
00:21:33,920 --> 00:21:39,000
sockets to web and not You're 
saying proprietary protocol that

326
00:21:39,000 --> 00:21:42,560
our purpose built for your 
native application. 

327
00:21:42,600 --> 00:21:49,400
This is sort of like why use? 
Why deploy a single or a few 

328
00:21:49,400 --> 00:21:53,440
pushpin and try to do it 
yourself where someone already 

329
00:21:53,440 --> 00:21:56,520
sold all of the hard parts on 
it. 

330
00:21:57,480 --> 00:22:01,120
And at the scale we have, it's 
probably going to cost you less 

331
00:22:01,120 --> 00:22:03,880
as well. 
No, for sure. 

332
00:22:04,120 --> 00:22:06,640
Now that is very very true. 
So nice. 

333
00:22:06,640 --> 00:22:08,080
Have you played anything with 
the fan? 

334
00:22:08,080 --> 00:22:11,800
Out I haven't developed stuff 
myself. 

335
00:22:11,800 --> 00:22:17,080
I have dabbled with it during my
boot camp fastly, of course, 

336
00:22:17,080 --> 00:22:21,320
when I joined four years ago and
I'm I'm I'm I've just dabbled. 

337
00:22:21,320 --> 00:22:24,880
I haven't built anything 
specific with it. 

338
00:22:25,720 --> 00:22:28,640
Have you? 
Yeah, I've used it for, you know

339
00:22:28,760 --> 00:22:32,520
what should we call it? 
My hobby project where basically

340
00:22:32,520 --> 00:22:36,160
our layer on data updates one of
them. 

341
00:22:37,440 --> 00:22:42,840
But we're we're basically I use 
I leverage fan out for a 

342
00:22:43,520 --> 00:22:46,240
messaging channel for for data 
updates. 

343
00:22:47,120 --> 00:22:50,600
Yeah, in this case I don't 
necessarily push the data, but 

344
00:22:50,600 --> 00:22:53,840
it's sort of like, hey, it says 
yeah, that new data available 

345
00:22:53,840 --> 00:22:58,760
and then it triggers a pull. 
So it is definitely doable. 

346
00:22:58,760 --> 00:23:01,480
You know, it's it was quite easy
in this case. 

347
00:23:01,480 --> 00:23:06,120
I used the compute app and I 
think that the most wasted code 

348
00:23:06,120 --> 00:23:10,040
was actually for also taking 
care of service and events and 

349
00:23:10,040 --> 00:23:14,880
long and and polling. 
So but fan out was definitely 

350
00:23:14,880 --> 00:23:18,200
the easiest route. 
Yeah, I I think you have to use 

351
00:23:18,200 --> 00:23:22,440
fan out and compute in order to 
to handle the incoming messages.

352
00:23:24,440 --> 00:23:29,440
But how? 
How would like in in detail you 

353
00:23:29,440 --> 00:23:32,680
would have your messages being 
sent from. 

354
00:23:34,640 --> 00:23:37,880
You would send your messages 
through the fan out API and the 

355
00:23:37,880 --> 00:23:43,200
client connects to a domain that
you have set up that is serving 

356
00:23:43,760 --> 00:23:46,360
fastly serving on that domain 
with a computer. 

357
00:23:46,880 --> 00:23:52,600
And then you add your logic in 
there, such as take the messages

358
00:23:52,600 --> 00:23:56,480
and replicate them to all of the
other people on the same topic 

359
00:23:58,360 --> 00:24:01,280
or do other stuff. 
Yeah. 

360
00:24:01,520 --> 00:24:05,080
So, so the, so the flow is sort 
of like the client would would 

361
00:24:05,400 --> 00:24:09,720
trying to connect. 
And I in my case I have two 

362
00:24:09,720 --> 00:24:14,640
channels, one for for 
performance data and one for 

363
00:24:14,640 --> 00:24:17,720
weather data. 
And so there's two connections 

364
00:24:17,720 --> 00:24:21,320
that goes in and then basically 
when every time I receive an 

365
00:24:21,320 --> 00:24:24,360
update for that data in the 
computer app, it triggers a 

366
00:24:24,360 --> 00:24:27,920
message on those channels. 
So, so the power and sort of 

367
00:24:27,920 --> 00:24:31,120
performance, then it goes like 
say, hey, new data on to the 

368
00:24:31,120 --> 00:24:33,000
performance channel says that 
hey, new data. 

369
00:24:33,520 --> 00:24:35,720
And when the weather updates, 
you know, it's, it's on The 

370
00:24:35,720 --> 00:24:38,920
Weather Channel. 
So then I can AC, you know, 

371
00:24:38,960 --> 00:24:41,400
independent of each other, 
update the information. 

372
00:24:41,400 --> 00:24:46,640
So it's it was, you know, it was
easy to set up both on the 

373
00:24:46,640 --> 00:24:50,800
compute side and also the logic 
on the on the client side was 

374
00:24:50,800 --> 00:24:53,080
really simple to add. 
Yeah, yeah. 

375
00:24:53,080 --> 00:24:56,120
Especially nowadays with Claude 
and Cursor and all of the other.

376
00:24:56,480 --> 00:24:58,680
This was pre Claude. 
This was pre Claude. 

377
00:24:58,680 --> 00:25:00,760
That's. 
Exactly how we're going to speak

378
00:25:00,760 --> 00:25:02,480
about the future now, pre 
Claude. 

379
00:25:05,120 --> 00:25:07,120
It's going to be like after the 
pandemic. 

380
00:25:07,120 --> 00:25:11,040
I remember thinking that you're 
going to watch movies and see 

381
00:25:11,040 --> 00:25:13,400
how people shake hands. 
In fact, that's going to be 

382
00:25:13,400 --> 00:25:14,440
weird. 
Exactly. 

383
00:25:14,560 --> 00:25:16,560
I agree. 
But I think we're back at 

384
00:25:16,560 --> 00:25:18,880
shaking hands again. 
So yeah, we are back. 

385
00:25:18,880 --> 00:25:19,680
We are back. 
Yeah. 

386
00:25:19,680 --> 00:25:23,360
Sometimes it can be weird when 
someone points an elbow at you. 

387
00:25:23,760 --> 00:25:25,200
Yeah. 
And he's just going to grab. 

388
00:25:25,360 --> 00:25:27,960
He's going for the hug instead. 
Oh. 

389
00:25:31,200 --> 00:25:35,720
Well, that's true, I think. 
Yeah, sorry. 

390
00:25:35,720 --> 00:25:36,360
Go ahead. 
Listen. 

391
00:25:36,680 --> 00:25:38,080
Yeah, I was proud to take this 
over. 

392
00:25:38,080 --> 00:25:41,800
I promise that you guys not to 
have a 4 to 5 minutes episode 

393
00:25:41,800 --> 00:25:45,240
this time. 
So I'm thinking it. 

394
00:25:45,240 --> 00:25:50,760
So just to wrap this up, I would
love to hear like the three like

395
00:25:50,800 --> 00:25:57,040
when should you use Websocket? 
Like 3 different times you 

396
00:25:57,040 --> 00:26:00,560
should use websockets and 
through different times you 

397
00:26:00,560 --> 00:26:04,120
should use fan out. 
I think it's super clear fan out

398
00:26:04,120 --> 00:26:06,800
is 1 to many. 
So example. 

399
00:26:07,640 --> 00:26:15,520
Example is stateful queue for 
instance online gaming, 

400
00:26:16,440 --> 00:26:21,680
something social, real time 
things if you. 

401
00:26:21,680 --> 00:26:25,040
Want to send the same 
information more than once? 

402
00:26:25,720 --> 00:26:29,760
Fan out. 
So I heard that was my best 

403
00:26:29,760 --> 00:26:35,440
teacher voice so. 
Yeah, I I think also that 

404
00:26:35,600 --> 00:26:40,000
Websockets is something you can 
always use if you already have 

405
00:26:40,000 --> 00:26:44,040
something existing and you're 
moving for it. 

406
00:26:44,280 --> 00:26:46,760
Let's say that you're starting 
with ACDM provider. 

407
00:26:47,760 --> 00:26:51,080
All of the, all of us in the 
market would probably have 

408
00:26:51,080 --> 00:26:54,840
something called websockets pass
through and things like that. 

409
00:26:54,840 --> 00:26:58,240
So you could start using 
Websockets through ACDM 

410
00:26:58,240 --> 00:27:00,400
provider, for instance, if 
you're already have something 

411
00:27:00,400 --> 00:27:03,400
existing. 
But if you if you're if you're 

412
00:27:03,400 --> 00:27:08,400
starting in 2026 with an idea, 
then fan out or push pin is the 

413
00:27:08,400 --> 00:27:10,800
way to go. 
Yeah, no, totally. 

414
00:27:10,800 --> 00:27:14,760
I, I would, I fully agree that 
it's all like, I would probably 

415
00:27:14,760 --> 00:27:18,000
opt for fan out even if it's 
sort of like web sockets and 

416
00:27:18,000 --> 00:27:22,480
maybe, you know, extensibility 
of of what I'm doing is probably

417
00:27:22,480 --> 00:27:25,520
the key here. 
So always turn out or always try

418
00:27:25,520 --> 00:27:27,920
to push for using fan out. 
Yeah, no. 

419
00:27:27,920 --> 00:27:30,320
If I'm going to start build 
something, if I'm going to start

420
00:27:30,320 --> 00:27:34,560
doing it and you know, why not 
add channels, ETC. 

421
00:27:34,600 --> 00:27:38,480
From this from the get go, even 
if it is sort of like a one to 

422
00:27:38,480 --> 00:27:41,240
one communication first. 
But then it's sort of like I, I,

423
00:27:41,360 --> 00:27:43,360
I have the infrastructure in 
place. 

424
00:27:43,800 --> 00:27:47,600
I don't have to do pass through.
I can terminate it on on someone

425
00:27:47,600 --> 00:27:51,040
else's server, IE fastly. 
I don't need to sort of like go 

426
00:27:51,040 --> 00:27:55,240
out and and build that 
infrastructure myself. 

427
00:27:55,880 --> 00:27:59,920
Then in the future if I want to 
extend that to have men one to 

428
00:27:59,920 --> 00:28:03,640
many type of communication, then
I already done the plumbing. 

429
00:28:04,000 --> 00:28:07,920
I just need to hook on to that. 
So it creates scalability. 

430
00:28:08,520 --> 00:28:09,600
Yeah, for sure. 
Yeah. 

431
00:28:09,880 --> 00:28:13,480
Yeah. 
Yeah, so makes sense. 

432
00:28:13,520 --> 00:28:17,000
So try to early on build with a 
like a fan out. 

433
00:28:17,280 --> 00:28:21,080
Yeah, fan out in mind and it is 
sort of just use it as as part 

434
00:28:21,080 --> 00:28:24,680
of your infrastructure. 
And then even if the you could 

435
00:28:24,680 --> 00:28:28,440
do it in websockets, then you 
know at some point in time you 

436
00:28:28,440 --> 00:28:30,600
might come up with another cool 
idea. 

437
00:28:33,400 --> 00:28:37,080
Very cool. 
So the lesson for today? 

438
00:28:37,800 --> 00:28:43,880
Fan out. 
No, I think, I think we're just 

439
00:28:43,880 --> 00:28:48,480
going to end on on, as Marcus 
said, like try to build one too 

440
00:28:48,480 --> 00:28:50,880
many. 
And and sure, we're biased by 

441
00:28:50,880 --> 00:28:55,160
working it fastly, but I think 
fan out or pushpin is, is a 

442
00:28:55,160 --> 00:29:01,040
superior technology and a modern
take on on a live messaging or 

443
00:29:01,080 --> 00:29:08,520
on a on a live update real time.
And I think everyone, yeah, 

444
00:29:08,520 --> 00:29:11,480
everyone wants to have like 
everything in build type, like 

445
00:29:11,480 --> 00:29:13,880
in performance. 
We all know, OK, we all know. 

446
00:29:14,000 --> 00:29:17,000
Obviously, again, we're from 
fasting, but yeah, it's. 

447
00:29:17,000 --> 00:29:21,640
Cool. 
Yes, I have to run because I 

448
00:29:21,640 --> 00:29:24,400
have actual work to do now. 
And I said that before we 

449
00:29:24,400 --> 00:29:28,480
started this podcast as well. 
Like we moved this session just 

450
00:29:28,480 --> 00:29:31,480
so I could do actual work. 
All right, I think that's a 

451
00:29:31,480 --> 00:29:34,280
good, good, good place to stop 
at anyway. 

452
00:29:34,480 --> 00:29:37,080
Yes, thank you. 
Thanks everyone for joining 

453
00:29:37,080 --> 00:29:39,760
today and watch out for the next
episode. 

454
00:29:39,760 --> 00:29:42,080
All right, we will see you with 
that bit. 

455
00:29:42,320 --> 00:29:42,960
Take care. 
Yes. 

456
00:29:43,440 --> 00:29:45,040
Thank you. 
Bye you. 

457
00:29:45,120 --> 00:29:45,440
Bye.
