1
00:00:01,080 --> 00:00:08,760
We have developed networking as a way to share resources and information and how that's achieved directly

2
00:00:09,000 --> 00:00:14,280
maps to the particular architecture of the networking operating systems that we have been using.

3
00:00:15,440 --> 00:00:21,410
Now, in this lecture, we are going to talk about the most common known application architecture that

4
00:00:21,410 --> 00:00:23,420
is peer to peer architecture.

5
00:00:24,200 --> 00:00:27,980
There are two main network types that you need to know about.

6
00:00:27,980 --> 00:00:33,920
The first one is peer to peer, and the second one is client to server, which are going to see in the

7
00:00:33,920 --> 00:00:34,690
next lecture.

8
00:00:35,270 --> 00:00:42,320
And by the way, it's really tough to tell the difference just by looking at the diagram or even by

9
00:00:42,320 --> 00:00:45,250
checking out like the video of the network.

10
00:00:46,340 --> 00:00:53,060
But the differences between peer-to-peer and client server architectures are pretty major there.

11
00:00:53,240 --> 00:00:55,190
They are not just physical differences.

12
00:00:55,190 --> 00:00:56,850
They are logical differences, too.

13
00:00:57,930 --> 00:00:59,900
Now, you'll see what I mean in a bit.

14
00:01:00,590 --> 00:01:03,350
So what is a peer to peer network architecture?

15
00:01:03,680 --> 00:01:11,810
Well, computers connected together in peer to peer architecture do not have any central or special

16
00:01:11,810 --> 00:01:18,010
authority that all peers, meaning that when it comes to authority, they're all equals.

17
00:01:18,380 --> 00:01:20,720
For example, your group of friends.

18
00:01:20,720 --> 00:01:21,220
Right.

19
00:01:21,240 --> 00:01:25,000
No one has the authority to judge you or to decide who is greater.

20
00:01:25,430 --> 00:01:31,670
But when a teacher enters in a classroom, the teacher has the moral authority that is an example of

21
00:01:31,670 --> 00:01:32,920
clients of architecture.

22
00:01:33,710 --> 00:01:40,760
Then the authority to perform a security check for proper access rights lies with the computer that

23
00:01:40,760 --> 00:01:44,120
has the desired resources being requested from it.

24
00:01:45,650 --> 00:01:53,060
Now, it also means that computers existing in a peer to peer network can be confined to machines that

25
00:01:53,060 --> 00:01:59,270
access resources and server machines and provide those resources to other computers.

26
00:02:00,050 --> 00:02:06,260
Now, peer to peer network architecture is perfectly fine for less number of hosts.

27
00:02:06,270 --> 00:02:13,280
But if you're trying to have more than 50 or even 100 computers in a peer to peer network architecture,

28
00:02:13,640 --> 00:02:15,890
then it becomes a tedious task.

29
00:02:17,460 --> 00:02:24,570
If your network is running Windows, Mac or Unix in a local area network workgroup, you have to have

30
00:02:24,810 --> 00:02:26,850
a peer to peer network.

31
00:02:28,290 --> 00:02:35,640
Now, when it comes to peer-to-peer architecture, security is not centrally governed, each and every

32
00:02:35,640 --> 00:02:41,880
user has to remember and maintain a list of users and passwords on each and every machine.

33
00:02:43,170 --> 00:02:49,920
Worse, some of all those important passwords for the same users change on different machines, even

34
00:02:49,920 --> 00:02:51,420
for accessing resources.

35
00:02:51,720 --> 00:02:53,280
It's a total mess.

36
00:02:54,360 --> 00:03:01,290
And since every user has to remember the usernames and passwords of other computers, a lot of memory

37
00:03:01,290 --> 00:03:03,900
is required in this type of architecture.

38
00:03:05,130 --> 00:03:07,610
For example, as you can see on the screen.

39
00:03:07,660 --> 00:03:10,720
This is an example of peer-to-peer network architecture.

40
00:03:11,250 --> 00:03:16,140
Now, Millie, Pluto, Mickey and Louie are four types of users.

41
00:03:16,410 --> 00:03:23,930
And as you can see on the screen, each user is storing the passwords of remaining three now.

42
00:03:24,240 --> 00:03:30,300
For example, if Pluto wants to access the resources of Mickey and Mickey has to remember the password

43
00:03:30,300 --> 00:03:32,500
of Pluto, this is such a mess.

44
00:03:32,790 --> 00:03:38,010
Now, this seems okay for four computers, but what if there are hundreds of thousands of computers?

45
00:03:38,460 --> 00:03:44,190
Then is it possible to store all the information in 2000 computers of each and every year?

46
00:03:44,520 --> 00:03:48,450
No, that would take up a lot of time and a lot of memory.

47
00:03:48,490 --> 00:03:54,720
We do not have that much of a memory just to store usernames and passwords and to tackle this problem.

48
00:03:54,990 --> 00:03:57,780
Client server architecture is.

49
00:03:58,890 --> 00:04:07,530
Used in today's most of the business applications in the next lecture will have a look at client server

50
00:04:07,530 --> 00:04:08,630
network architecture.

