WEBVTT 1 00:00.000 --> 00:08.440 Finally, let's wrap up by looking at some of the features offered by Google 2 00:08.440 --> 00:09.600 Cloud Platform, 3 00:09.600 --> 00:11.520 which as we're going to see, 4 00:11.520 --> 00:15.920 these are very similar in nature to the features that we've already discussed, 5 00:15.920 --> 00:20.440 coming from Amazon AWS and Microsoft Azure. 6 00:20.440 --> 00:24.600 Now, that shouldn't be a big surprise because as we said at the very beginning, 7 00:24.600 --> 00:28.040 most of these Cloud providers offer very similar features. 8 00:28.040 --> 00:32.180 So let's just go ahead and jump in and take a look to wrap up the big three WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 8 00:28.040 --> 00:32.180 So let's just go ahead and jump in and take a look to wrap up the big three 9 00:32.180 --> 00:33.480 Cloud providers, 10 00:33.480 --> 00:37.840 and we'll take a look at some of these different details and some of the naming 11 00:37.840 --> 00:40.040 that might be a little bit different. 12 00:40.040 --> 00:46.680 So let's start off here a little bit by talking about the GCP architecture. 13 00:46.680 --> 00:52.000 And much like AWS, we also use global regions. 14 00:52.000 --> 00:59.170 And within those regions, we have availability zones that are again, just like 15 00:59.170 --> 00:59.960 AWS, 16 00:59.960 --> 01:05.280 isolated locations, and they are completely independent. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 16 00:59.960 --> 01:05.280 isolated locations, and they are completely independent. 17 01:05.280 --> 01:09.860 They have their own redundant power, they have redundant cooling, redundant 18 01:09.860 --> 01:11.000 networking. 19 01:11.000 --> 01:14.840 Again, each one is its own standalone data center. 20 01:14.840 --> 01:21.240 And in a similar fashion, deploying applications across multiple zones within 21 01:21.240 --> 01:22.440 the same region 22 01:22.440 --> 01:27.040 will protect against failures of those particular zones. 23 01:27.040 --> 01:30.580 And we're not really saying it here, but of course, you can also distribute WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 23 01:27.040 --> 01:30.580 And we're not really saying it here, but of course, you can also distribute 24 01:30.580 --> 01:32.440 things between regions. 25 01:32.440 --> 01:36.680 It just gets a little bit trickier as far as how you're going to load share 26 01:36.680 --> 01:36.680 those. 27 01:36.680 --> 01:42.680 But just like Microsoft Azure, we also have global load balancing. 28 01:42.680 --> 01:47.400 With global load balancing, this is going to be globally distributed. 29 01:47.400 --> 01:53.240 And therefore, it can automatically route users to the nearest available 30 01:53.240 --> 01:54.280 instance. 31 01:54.280 --> 01:58.520 This is again going to be based on their geographic location. 32 01:58.520 --> 02:03.600 So again, we can see how this is very similar to the offerings of the other WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 32 01:58.520 --> 02:03.600 So again, we can see how this is very similar to the offerings of the other 33 02:03.600 --> 02:04.920 Cloud providers. 34 02:04.920 --> 02:10.760 And as would be expected, this traffic can be rerouted if there's either a zone 35 02:10.760 --> 02:12.600 or a region failure. 36 02:12.600 --> 02:17.150 So if something goes wrong, we can simply reroute the traffic to a zone or a 37 02:17.150 --> 02:19.960 region that is still functional. 38 02:19.960 --> 02:25.840 And finally, again, much like other providers, we also can do either dedicated 39 02:25.840 --> 02:26.520 internet 40 02:26.520 --> 02:31.080 or partner internet access to GCP. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 40 02:26.520 --> 02:31.080 or partner internet access to GCP. 41 02:31.080 --> 02:36.200 This is going to provide a direct connection to the Google Cloud platform 42 02:36.200 --> 02:39.000 from your on-premises data centers. 43 02:39.000 --> 02:43.550 And just like we saw with direct connections previously, this is going to 44 02:43.550 --> 02:45.080 enhance redundancy, 45 02:45.080 --> 02:49.640 because again, you could be using either the dedicated interconnect or partner 46 02:49.640 --> 02:50.360 interconnect 47 02:50.360 --> 02:53.720 in conjunction with normal internet access. 48 02:53.720 --> 02:55.800 So this can be acting as a backup. 49 02:55.800 --> 03:00.820 Now, this is, of course, generally going to have reduced latency compared to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 49 02:55.800 --> 03:00.820 Now, this is, of course, generally going to have reduced latency compared to 50 03:00.820 --> 03:01.640 something like the 51 03:01.640 --> 03:04.280 internet, because it is a dedicated connection. 52 03:05.240 --> 03:11.160 And as part of this, Google has the Content Delivery Network or the CDN, 53 03:11.160 --> 03:16.520 which is part of Google's Global Network, which allows for things like global 54 03:16.520 --> 03:17.640 distribution 55 03:17.640 --> 03:23.080 of your resources and your servers, does caching at the network edge, 56 03:23.080 --> 03:26.040 so that we don't necessarily have to go to your servers. 57 03:26.040 --> 03:28.840 They can cache responses for your clients. 58 03:29.400 --> 03:36.760 And much like we've seen previously, this will do HTTP and HTTPS offload, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 58 03:29.400 --> 03:36.760 And much like we've seen previously, this will do HTTP and HTTPS offload, 59 03:36.760 --> 03:40.760 so that we don't have to load down the servers with doing decryption. 60 03:40.760 --> 03:46.680 So again, much of the same type services that we saw with the other providers. 61 03:46.680 --> 03:52.500 So in this video, we wrapped up our skill by taking a look at some of the 62 03:52.500 --> 03:54.040 offerings available 63 03:54.040 --> 04:00.120 on the Google Cloud platform. And like we saw and as was expected, we saw a lot WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 63 03:54.040 --> 04:00.120 on the Google Cloud platform. And like we saw and as was expected, we saw a lot 64 04:00.120 --> 04:01.400 of the same features 65 04:01.400 --> 04:04.440 that we have on the big three cloud providers. 66 04:04.440 --> 04:09.310 And that's really to be expected because the customers expect the same level of 67 04:09.310 --> 04:10.040 service. 68 04:10.040 --> 04:15.260 So that concludes everything that we need to discuss in this skill, which 69 04:15.260 --> 04:16.760 leaves us with just 70 04:16.760 --> 04:21.150 the challenge. So go ahead and give that a shot, and I'll see you in the 71 04:21.150 --> 04:23.080 solution video on the other side. 72 04:23.080 --> 04:23.580 Bye.