WEBVTT

1
00:00.000 --> 00:08.270
So in our previous skill, we spent a lot of time focusing on private network

2
00:08.270 --> 00:11.000
connections to our cloud providers.

3
00:11.000 --> 00:14.000
And of course, that's always still an option.

4
00:14.000 --> 00:21.150
But a cloud exchange is a third party provider that provides us with a private

5
00:21.150 --> 00:26.000
connection to multiple cloud providers through a single connection.

6
00:26.000 --> 00:30.290
So rather than having a separate connection out to each one individually, we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

6
00:26.000 --> 00:30.290
So rather than having a separate connection out to each one individually, we

7
00:30.290 --> 00:33.000
can instead go through a cloud exchange.

8
00:33.000 --> 00:36.980
So let's go ahead and jump in, look at some details of that, see some of the

9
00:36.980 --> 00:44.000
advantages, and we'll take a look at a diagram of how this all fits together.

10
00:44.000 --> 00:49.840
So again, remembering that a cloud exchange is a third party provider to

11
00:49.840 --> 00:53.000
connect you to multiple cloud providers.

12
00:53.000 --> 00:57.610
Let's talk about some of the benefits that that's going to offer as opposed to

13
00:57.610 --> 01:02.390
having private connections to each one individually, or just connecting over
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:57.610 --> 01:02.390
having private connections to each one individually, or just connecting over

14
01:02.390 --> 01:04.000
the traditional internet.

15
01:04.000 --> 01:08.000
Well, the first one is we're generally going to have higher performance.

16
01:08.000 --> 01:12.890
Since this is going to be running as a private connection, it's generally going

17
01:12.890 --> 01:15.000
to be a high performance link.

18
01:15.000 --> 01:19.000
And with that generally comes low latency as well.

19
01:19.000 --> 01:23.940
So it's probably going to be high throughput, low latency, and since it's

20
01:23.940 --> 01:30.310
generally a private connection, that's also going to mean increased security,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
01:23.940 --> 01:30.310
generally a private connection, that's also going to mean increased security,

21
01:30.310 --> 01:34.000
particularly compared to going over the public internet.

22
01:34.000 --> 01:39.600
And again, of course, its primary benefit is the fact that it connects to

23
01:39.600 --> 01:43.000
multiple cloud providers simultaneously.

24
01:43.000 --> 01:48.400
For ease of management, it's generally going to involve some form of a web

25
01:48.400 --> 01:52.990
portal that you're going to be able to use to control that cloud access,

26
01:52.990 --> 01:57.000
meaning of course, which cloud providers you want to connect to.

27
01:57.000 --> 02:03.800
Now, for the most part, these cloud exchanges are probably going to charge some
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
01:57.000 --> 02:03.800
Now, for the most part, these cloud exchanges are probably going to charge some

28
02:03.800 --> 02:10.310
form of a sign up fee for your initial connectivity, then possibly a set up fee

29
02:10.310 --> 02:15.000
for each cloud provider that you want to connect to.

30
02:15.000 --> 02:19.610
There's also going to be a monthly service fee, of course, which is your

31
02:19.610 --> 02:26.380
ongoing payment for the service. So really, let's take a look at how this

32
02:26.380 --> 02:30.000
compares to a private connection.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

33
02:30.000 --> 02:35.310
So in this diagram, we have a server down here at the bottom, which is meant to

34
02:35.310 --> 02:38.000
represent the corporate network.

35
02:38.000 --> 02:43.820
And we also have just for reference here, an example of a direct connection or

36
02:43.820 --> 02:48.000
a private connection out to say, for example, AWS.

37
02:48.000 --> 02:52.900
So this is what we were talking about in our previous skill, when we were

38
02:52.900 --> 02:57.000
talking about private connections to cloud providers.

39
02:57.000 --> 03:02.470
And of course, the big thing that changes here with a cloud exchange is we're
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
02:57.000 --> 03:02.470
And of course, the big thing that changes here with a cloud exchange is we're

40
03:02.470 --> 03:08.000
now going to have this single connection going out to the cloud exchange.

41
03:08.000 --> 03:17.390
And then of course, the cloud exchange is in turn going to connect us out to

42
03:17.390 --> 03:23.000
say AWS or Google IBM, Azure, and so on.

43
03:23.000 --> 03:28.650
And of course, going to depend on which cloud providers, this particular cloud

44
03:28.650 --> 03:31.000
exchange has connections to.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

44
03:28.650 --> 03:31.000
exchange has connections to.

45
03:31.000 --> 03:36.000
But overall, this is the basic idea behind a cloud exchange.

46
03:36.000 --> 03:40.550
We're going to have a single connection to the cloud exchange, and then we can

47
03:40.550 --> 03:45.510
use that connection to connect out to any other cloud providers that we want to

48
03:45.510 --> 03:46.000
connect to.

49
03:46.000 --> 03:52.160
So in this video, we discussed cloud exchanges and how we can use this third

50
03:52.160 --> 04:05.330
party service to connect to multiple different cloud providers through a single
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

50
03:52.160 --> 04:05.330
party service to connect to multiple different cloud providers through a single

51
04:05.330 --> 04:14.000
connection.

52
04:14.000 --> 04:20.390
And the next thing that we're going to discuss is software defined cloud inter

53
04:20.390 --> 04:22.000
connect or SDCI.

54
04:22.000 --> 04:25.000
And that's exactly what we're going to do in the next video.