1
00:00:00,180 --> 00:00:06,420
All right, and welcome to our next project, The Story API, where we'll learn the advanced filtering,

2
00:00:06,420 --> 00:00:11,390
sorting and dynamically populating our database, as well as a bunch of other cool stuff.

3
00:00:11,790 --> 00:00:17,330
While I did not create the front end for this project just because it seemed like an oracle that is

4
00:00:17,340 --> 00:00:17,810
following.

5
00:00:18,090 --> 00:00:24,930
Imagine we are in charge of store API and we want to provide a bunch of search options for our users.

6
00:00:25,260 --> 00:00:30,120
Everything, starting with search by name, do filtering based on price amount.

7
00:00:30,600 --> 00:00:34,380
Since we'll cover all the options in great detail during the project.

8
00:00:34,710 --> 00:00:40,620
I won't do it right now, but I do want to showcase where I got the idea from and how that would look

9
00:00:40,620 --> 00:00:41,520
like in real life.

10
00:00:41,790 --> 00:00:46,530
And it's probably not going to be surprised if I tell you that I got this idea from the Hacker News

11
00:00:46,530 --> 00:00:52,460
API and if you remember, they offer quite a few search options for their user.

12
00:00:52,890 --> 00:00:57,810
Now, we're not going to implement all of them, but we will mimic the major ones.

13
00:00:58,050 --> 00:01:03,240
And as far as how it's going to look like in real life, if you took my real course, you probably worked

14
00:01:03,240 --> 00:01:04,319
on a store project.

15
00:01:04,709 --> 00:01:09,210
And during that project, we built the entire search functionality on the front end.

16
00:01:09,780 --> 00:01:17,820
Now, imagine, once we're done building our API, the front end only needs to make HTP calls and we

17
00:01:17,820 --> 00:01:18,810
send back the data.

18
00:01:19,260 --> 00:01:26,490
So the same result user can still search for product, but only this time the backend does all the heavy

19
00:01:26,490 --> 00:01:26,940
lifting.

20
00:01:27,360 --> 00:01:33,990
And Fronton is only responsible for Ishita pixels so the user can still search for product, whether

21
00:01:33,990 --> 00:01:38,210
that's based on name or category more company.

22
00:01:38,220 --> 00:01:39,740
And of course you can read the rest.

23
00:01:40,170 --> 00:01:47,670
But the difference is, of course, that now the front end only makes the call and then the backend

24
00:01:47,850 --> 00:01:49,560
does all the heavy lifting.