1
00:00:00,450 --> 00:00:04,140
-: Performance is one of the most important aspects

2
00:00:04,140 --> 00:00:07,500
of web apps, and specifically web API.

3
00:00:07,500 --> 00:00:10,410
You must make sure your API is fast

4
00:00:10,410 --> 00:00:14,220
in that it provides quick responses for the developers.

5
00:00:14,220 --> 00:00:16,230
Now, why is that?

6
00:00:16,230 --> 00:00:20,850
What makes performance so important for the web API?

7
00:00:20,850 --> 00:00:23,310
Well, this is one of the reasons.

8
00:00:23,310 --> 00:00:26,910
According to Google, 53% of mobile users

9
00:00:26,910 --> 00:00:30,630
abandon sites that take over three seconds to load.

10
00:00:30,630 --> 00:00:32,580
Now, I'm not sure what is the exact number

11
00:00:32,580 --> 00:00:36,120
for API users and not mobile users,

12
00:00:36,120 --> 00:00:39,270
but my guess is they are pretty close.

13
00:00:39,270 --> 00:00:42,810
So your users will simply abandon your API

14
00:00:42,810 --> 00:00:45,120
if it's not fast enough.

15
00:00:45,120 --> 00:00:48,810
So your API must be fast.

16
00:00:48,810 --> 00:00:50,580
Now, it's important to note

17
00:00:50,580 --> 00:00:54,450
that performance is not directly related to the API,

18
00:00:54,450 --> 00:00:57,360
but it is actually related to the underlying code.

19
00:00:57,360 --> 00:00:59,520
So the techniques we are going to discuss

20
00:00:59,520 --> 00:01:03,630
in this section are not strictly about the API,

21
00:01:03,630 --> 00:01:07,140
but more about the code executed underlying it.

22
00:01:07,140 --> 00:01:10,200
But still, these are important techniques

23
00:01:10,200 --> 00:01:11,910
and you must be aware of them.

24
00:01:11,910 --> 00:01:14,460
So let's review some performance techniques

25
00:01:14,460 --> 00:01:16,080
that will probably improve

26
00:01:16,080 --> 00:01:18,393
your API performance significantly.