1
00:00:00,000 --> 00:00:03,986
[MUSIC]

2
00:00:03,986 --> 00:00:06,862
[SOUND] Hi, my name is James.

3
00:00:06,862 --> 00:00:11,847
In earlier Treehouse content, we've
seen how ASP.NET can be used to create

4
00:00:11,847 --> 00:00:17,480
web applications containing server
side rendered user interfaces, or UIs.

5
00:00:17,480 --> 00:00:22,250
These applications allow users to work
with data, execute steps in a work flow,

6
00:00:22,250 --> 00:00:25,380
or monitor automated processes.

7
00:00:25,380 --> 00:00:28,477
This is a common use case for ASP.NET, but

8
00:00:28,477 --> 00:00:33,490
ASP.net can also be used to create
applications that expose data in

9
00:00:33,490 --> 00:00:39,120
processes through application
programming interfaces, or APIs.

10
00:00:39,120 --> 00:00:40,390
These applications or

11
00:00:40,390 --> 00:00:45,310
services are typically implemented
using public standards or guidelines.

12
00:00:45,310 --> 00:00:47,280
That makes it easier for third parties or

13
00:00:47,280 --> 00:00:52,580
developers to understand how to
consume and use our services.

14
00:00:52,580 --> 00:00:56,980
Services give us a way to decouple
our back end from our front end.

15
00:00:56,980 --> 00:01:01,800
Front end clients don't need to know all
the implementation details of the service.

16
00:01:01,800 --> 00:01:06,130
They only need to understand how
to work with the service's API.

17
00:01:06,130 --> 00:01:09,720
Separation between the back end and
the front end makes it easy for

18
00:01:09,720 --> 00:01:13,910
our services to support
multiple front end clients, or

19
00:01:13,910 --> 00:01:18,630
even to integrate with other services
enabling machine to machine communication.

20
00:01:19,840 --> 00:01:22,283
Services are not a new idea.

21
00:01:22,283 --> 00:01:27,306
The origins of proprietary computer
to computer communication protocols,

22
00:01:27,306 --> 00:01:32,650
known as remote procedure calls, or RPC,
date all the way back to the 1970s.

23
00:01:33,730 --> 00:01:37,830
And in the early 2000s,
developers combined HTTP and

24
00:01:37,830 --> 00:01:41,928
SOAP to create a new class of
services known as Web Services.

25
00:01:41,928 --> 00:01:46,880
Developers, who were looking for
a simpler, yet still powerful to build

26
00:01:46,880 --> 00:01:52,410
services, eventually,
embraced RESTful Services or APIs.

27
00:01:52,410 --> 00:01:56,140
Instead of introducing new or
proprietary technology,

28
00:01:56,140 --> 00:01:59,700
REST APIs leverage the native
capabilities of HTTP.

29
00:02:00,980 --> 00:02:05,950
In this course, you'll learn how to use
Microsoft's ASP.NET Web API framework to

30
00:02:05,950 --> 00:02:07,850
build a rest API.

31
00:02:07,850 --> 00:02:11,130
As you learn about web API,
you'll be creating a service for

32
00:02:11,130 --> 00:02:13,010
Fitness Frog Web Client.

33
00:02:13,010 --> 00:02:16,680
A single page application,
or spa, built using Angular.

34
00:02:17,710 --> 00:02:22,490
To get the most out of this course, you
should understand the basics of REST APIs

35
00:02:22,490 --> 00:02:29,810
and be familiar with C#, ASP.NET, MVC,
Entity Framework, and Visual Studio.

36
00:02:29,810 --> 00:02:34,710
If you're unfamiliar with any of these,
or maybe you need a refresher, see

37
00:02:34,710 --> 00:02:38,440
the teacher's notes for links to resources
that can help bring you up to speed.

38
00:02:39,470 --> 00:02:44,612
I would also encourage you to follow
along with each video as we design,

39
00:02:44,612 --> 00:02:47,452
build, and test the Fitness Frog API.

40
00:02:47,452 --> 00:02:50,299
By actively participating
in a learning process,

41
00:02:50,299 --> 00:02:54,480
you'll increased your retention of
the material covered in this course.

42
00:02:55,600 --> 00:03:00,780
In the next video, let's start with a
quick review of what makes an API RESTful.

43
00:03:00,780 --> 00:03:01,400
See you then.