WEBVTT

1
00:00:00.000 --> 00:00:01.920
In this lesson, we will learn

2
00:00:01.920 --> 00:00:04.140
about deployment strategies.

3
00:00:04.140 --> 00:00:05.948
To develop deployment strategies,

4
00:00:05.948 --> 00:00:09.439
we need to take into account how geography impacts

5
00:00:09.439 --> 00:00:13.830
performance, network redundancy, and compliance.

6
00:00:13.830 --> 00:00:17.084
These are also known as geographical considerations,

7
00:00:17.084 --> 00:00:19.440
and they play an important role

8
00:00:19.440 --> 00:00:22.080
in the planning of deployment strategies,

9
00:00:22.080 --> 00:00:24.715
and involve strategically placing infrastructure

10
00:00:24.715 --> 00:00:27.630
in dispersed physical locations.

11
00:00:27.630 --> 00:00:29.460
Geographical considerations

12
00:00:29.460 --> 00:00:31.860
for deployment strategies include

13
00:00:31.860 --> 00:00:36.750
optimizing performance, network redundancy, and compliance.

14
00:00:36.750 --> 00:00:40.110
Let's learn more about each of these considerations.

15
00:00:40.110 --> 00:00:43.500
First, we have optimizing performance.

16
00:00:43.500 --> 00:00:46.530
Optimizing performance focuses on ensuring

17
00:00:46.530 --> 00:00:50.430
applications run efficiently for users worldwide.

18
00:00:50.430 --> 00:00:52.994
A key tactic is reducing latency

19
00:00:52.994 --> 00:00:55.920
by deploying servers in different regions

20
00:00:55.920 --> 00:00:59.370
so users can connect to the nearest one.

21
00:00:59.370 --> 00:01:03.060
Tools like content delivery networks, or CDNs,

22
00:01:03.060 --> 00:01:05.374
help by caching content closer to users

23
00:01:05.374 --> 00:01:07.980
to speed up load times.

24
00:01:07.980 --> 00:01:11.460
Load balancing also optimizes performance.

25
00:01:11.460 --> 00:01:13.794
Tools like Amazon Web Services,

26
00:01:13.794 --> 00:01:18.330
or AWS Elastic Load Balancing, or NGINX,

27
00:01:18.330 --> 00:01:21.750
ensure traffic is evenly distributed across servers,

28
00:01:21.750 --> 00:01:23.310
preventing overload.

29
00:01:23.310 --> 00:01:25.140
Additionally, auto-scaling

30
00:01:25.140 --> 00:01:29.400
with services like AWS Auto-Scaling automatically adjust

31
00:01:29.400 --> 00:01:32.850
the number of production servers based on demand,

32
00:01:32.850 --> 00:01:36.870
ensuring a smooth performance during traffic spikes.

33
00:01:36.870 --> 00:01:41.220
Our last technology to optimize performance is caching.

34
00:01:41.220 --> 00:01:46.020
Tools like Redis or Memcached store frequently accessed data

35
00:01:46.020 --> 00:01:50.340
for quicker retrieval, reducing the strain on databases.

36
00:01:50.340 --> 00:01:54.870
Combining geographical server distribution, load balancing,

37
00:01:54.870 --> 00:01:57.900
auto-scaling and caching ensures

38
00:01:57.900 --> 00:02:02.610
fast responsive applications that can handle traffic spikes.

39
00:02:02.610 --> 00:02:06.240
Our next consideration is network redundancy.

40
00:02:06.240 --> 00:02:08.040
Network redundancy ensures

41
00:02:08.040 --> 00:02:12.360
that services keep running smoothly, even if a system fails.

42
00:02:12.360 --> 00:02:15.630
This is like having a backup route to drive to work.

43
00:02:15.630 --> 00:02:17.190
If one road is blocked,

44
00:02:17.190 --> 00:02:19.860
another road gets you to where you need to go.

45
00:02:19.860 --> 00:02:22.080
Companies achieve network redundancy

46
00:02:22.080 --> 00:02:26.310
by deploying infrastructure in multiple physical locations.

47
00:02:26.310 --> 00:02:30.030
That way if one server or data center goes down,

48
00:02:30.030 --> 00:02:32.460
another can immediately take over.

49
00:02:32.460 --> 00:02:37.410
In implementing redundancy, tools like AWS Route 53

50
00:02:37.410 --> 00:02:41.130
or Azure Traffic Manager help reroute traffic

51
00:02:41.130 --> 00:02:44.820
to available servers, ensuring minimal disruption.

52
00:02:44.820 --> 00:02:48.117
Additionally, using multi-region failover systems

53
00:02:48.117 --> 00:02:51.240
also provides backup continuity

54
00:02:51.240 --> 00:02:53.725
by switching to another operational region

55
00:02:53.725 --> 00:02:56.250
when one region fails.

56
00:02:56.250 --> 00:02:58.654
Finally, we have compliance.

57
00:02:58.654 --> 00:03:02.730
Compliance is a critical factor that can't be overlooked,

58
00:03:02.730 --> 00:03:05.700
especially when dealing with infrastructure spread

59
00:03:05.700 --> 00:03:08.970
across multiple geographical locations.

60
00:03:08.970 --> 00:03:10.830
Compliance refers to following

61
00:03:10.830 --> 00:03:12.999
the laws and regulations that dictate

62
00:03:12.999 --> 00:03:17.310
how data must be stored, processed, and protected.

63
00:03:17.310 --> 00:03:19.980
These rules vary from country to country,

64
00:03:19.980 --> 00:03:21.820
which can complicate operations

65
00:03:21.820 --> 00:03:24.480
when your infrastructure is global.

66
00:03:24.480 --> 00:03:26.730
For example, in Europe,

67
00:03:26.730 --> 00:03:30.720
the General Data Protection Regulation, or GDPR,

68
00:03:30.720 --> 00:03:34.515
implements strict rules about how personal data is handled,

69
00:03:34.515 --> 00:03:37.194
including where it can be stored,

70
00:03:37.194 --> 00:03:41.640
and how the data subject is able to control their data.

71
00:03:41.640 --> 00:03:44.550
To ensure compliance on a global scale,

72
00:03:44.550 --> 00:03:48.333
companies might use tools like AWS Compliance Center

73
00:03:48.333 --> 00:03:51.856
or Azure Policy to help manage data storage

74
00:03:51.856 --> 00:03:55.680
and processing in line with local laws.

75
00:03:55.680 --> 00:03:59.007
These tools allow businesses to set specific rules

76
00:03:59.007 --> 00:04:01.698
about where their data can be stored

77
00:04:01.698 --> 00:04:03.756
and how it should be handled

78
00:04:03.756 --> 00:04:06.540
to meet regulatory requirements.

79
00:04:06.540 --> 00:04:09.646
For instance, compliance tools may restrict data

80
00:04:09.646 --> 00:04:12.869
to only being stored in specific regions

81
00:04:12.869 --> 00:04:16.110
to comply with local regulations.

82
00:04:16.110 --> 00:04:19.320
Another challenge comes with data residency,

83
00:04:19.320 --> 00:04:22.602
where some laws require that certain types of data,

84
00:04:22.602 --> 00:04:25.380
such as financial or health data,

85
00:04:25.380 --> 00:04:28.833
remain within the country where it was collected.

86
00:04:28.833 --> 00:04:32.894
To handle this, businesses can use multi-region setups

87
00:04:32.894 --> 00:04:35.673
that store data in specific locations

88
00:04:35.673 --> 00:04:38.340
to comply with these laws,

89
00:04:38.340 --> 00:04:41.573
while still benefiting from a global infrastructure.

90
00:04:41.573 --> 00:04:44.280
By using these tools and strategies,

91
00:04:44.280 --> 00:04:46.159
companies can balance performance,

92
00:04:46.159 --> 00:04:49.220
network redundancy and compliance,

93
00:04:49.220 --> 00:04:51.936
ensuring that they meet legal obligations

94
00:04:51.936 --> 00:04:55.398
while optimizing their infrastructure deployment.

95
00:04:55.398 --> 00:04:59.511
So remember, when planning deployment strategies,

96
00:04:59.511 --> 00:05:01.350
it's important to consider

97
00:05:01.350 --> 00:05:03.780
how geography impacts performance,

98
00:05:03.780 --> 00:05:06.780
network redundancy and compliance.

99
00:05:06.780 --> 00:05:09.960
Optimizing performance involves placing infrastructure

100
00:05:09.960 --> 00:05:13.110
in different locations to reduce latency

101
00:05:13.110 --> 00:05:15.660
and improve speed for users.

102
00:05:15.660 --> 00:05:17.370
Network redundancy ensures

103
00:05:17.370 --> 00:05:20.778
services remain available even if a system fails

104
00:05:20.778 --> 00:05:25.407
by having backup systems in place across multiple locations,

105
00:05:25.407 --> 00:05:29.441
and compliance focuses on following local laws regarding

106
00:05:29.441 --> 00:05:31.650
data storage and processing,

107
00:05:31.650 --> 00:05:33.640
which can vary from country to country

108
00:05:33.640 --> 00:05:36.333
and require careful planning.