-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
256 lines (187 loc) · 5.95 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta
name="viewport"
content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=0"
/>
<title>Unsuck API integrations with Superface</title>
<link href="big.css" rel="stylesheet" type="text/css" />
<link rel="stylesheet" href="themes/sf.css" />
<script src="big.js"></script>
</head>
<body>
<div>
<h1>Unsuck <em>API Integrations</em></h1>
<small class="nowrap">DKSS by Cookielab, 1. 10. 2021</small><br />
<small class="nowrap">Jan Vlnas, Superface</small>
<notes>Speakers notes go here.</notes>
</div>
<div>Developer advocate</div>
<div>API integrations? 🤔</div>
<div>
Send <em>email</em><br />
Track <em>parcel</em><br />
Get <em>weather</em><br />
Fetch <em>ad metrics</em>
<div class="nowrap">Send <em>event</em> to analytics</div>
</div>
<div>
<span class="sm">3rd</span> parties<br />&<br />Internal APIs
</div>
<div>
<em class="nowrap"><span class="sm">3rd</span> parties</em>
<br />&<br />Internal APIs
</div>
<div><em>Capabilities</em></div>
<div>API integrations <em>suck</em></div>
<div>
API integrations suck<em>?</em>
<notes>✋ Raise your hand if you agree</notes>
</div>
<div>
<em>Why</em> they suck?
<notes></notes>
</div>
<div class="nowrap sm">(rant ahead)</div>
<div><em>Discovery</em> sucks</div>
<div>
<img src="img/search_email_api.png" alt="" style="max-height: 90vh" />
</div>
<div>
Is it <em>cheap</em>?<br />
Is it <em>easy</em>?<br />
Is it <em>reliable</em>?
</div>
<div>Too many <em>options</em></div>
<div>
<img src="img/github_products.png" alt="" />
</div>
<div><em>Documentation</em> sucks</div>
<div class="sm">
<q>I want to list <em>repositories</em></q>
</div>
<div>
<img src="img/bitbucket.png" alt="" />
</div>
<div>
Doesn't solve <em>my</em> problem
<notes>Great your API is restful</notes>
</div>
<div><em>Functionality</em> sucks</div>
<div>Docs don't reflect <em>reality</em></div>
<!-- <div class="layout">
<img src="img/tumblr_docs.png" alt="" />
<notes> This is example from Tumblr API documentation. </notes>
</div> -->
<div>
<em>Interactive</em> examples
<notes>I'd rather call the API than to trust the documentation</notes>
</div>
<div>
<em>Maintenance</em> sucks
<notes>APIs evolve even if your use-case remains the same.</notes>
</div>
<!-- <div>
<img src="img/facebook_breaks_twitter.png" alt="">
</div> -->
<div>
<img src="img/strip_nicer.png" alt="" />
</div>
<div><em>Outages</em> suck</div>
<div><img src="img/tweet_email.png" alt="" /></div>
<div>
Integration<br />is<br /><em>liability</em>
<notes>Maybe it works for now, but it may come later and bite you.</notes>
</div>
<div>
<em>Machine</em> to<br />
<em>machine</em> communication<br />
</div>
<div>
<em>Machine</em> to<br />
<em>machine</em> communication<br />
<small class="sm">is fiction</small>
</div>
<!-- <div>TODO Orly?</div> -->
<div>
🧑🏾💻 build API<br />
🧑🏼💻 write docs<br />
<hr />
👩🏻💻 read docs<br />
👩🏻💻 write integration<br />
</div>
<div>
<em>Humans</em> to<br />
<em>humans</em> communication<br />
<small>via docs</small>
</div>
<div>What can we <em>do</em> about it?</div>
<div>
<img src="img/strip_worship.png" alt="" />
</div>
<div>More tooling?</div>
<div class="layout">
<img src="img/api_landscape.png" alt="" />
</div>
<div>Curing <em>symptoms</em>, not <em>disease</em></div>
<div><small class="nowrap">(sales pitch ahead)</small></div>
<div class="layout">
<img src="img/superface.svg" alt="" style="display: block" />
</div>
<div>Principles</div>
<div><em>Use-cases</em> not HTTP calls</div>
<div>
Think <code class="nowrap em">Send Email</code><br />
not <code class="nowrap em">POST /email</code>
</div>
<div>
<em>Use-cases</em> not providers
<notes>Think what happens if your provider is down.</notes>
</div>
<div>
<img src="img/strip_implementation.png" alt="" />
</div>
<div><em>Direct calls</em> not proxies</div>
<div class="sm">
iPaaS
<notes>
Do you know this acronym? Integration Platform as a service.<br />
They usually harmonize data inside their service. What if the
integration platform goes down?
</notes>
</div>
<div class="sm">
<s>iPaaS</s>
<notes
>Superface is not it. The calls go directly to providers. If Superface
services go down, it doesn't break running apps. Also, we don't need to
handle your sensitive information.</notes
>
</div>
<div><em>Runtime</em><br />not hardcoding</div>
<div>Handle API changes <em>without redeploy</em></div>
<div>
<em>Universal client</em> not custom ones
<notes>
At this moment some developer somewhere is implementing a bespoke client
for an API</notes
>
</div>
<div><em>How</em> does it work?</div>
<div class="layout">
<img src="img/how-superface-works.svg" alt="" style="display: block" />
</div>
<div>Demo</div>
<div>Where are we heading?</div>
<div><em class="nowrap">Self-integrating</em> apps</div>
<div>API Keys <em>management</em></div>
<div>Capabilities <em>marketplace</em></div>
<div><em>Universe</em> of capabilities</div>
<div>
<em class="sm">superface.ai/demoday</em>
</div>
</body>
</html>